Filter by reset
- Everywhere
131 - Issues
35 - Pull Requests
32 - Comments
64
Implementing a duration and the relative percentage for each command in a test seems like a great idea. We can use our existing block syntax and just overlook it during the test: ––– duration: 0.123ms (10.2%) –––
enhancement
Improve CLT output with user command
We should improve our CLI action and provide users with a given command that they can run to validate the test locally. In the same output, we should dump information about the script and real command execution.
Possibility to reset mistaken command in record session
It is indeed a great idea to include the option of undoing a mistaken command while we are in recording mode. This can be achieved by implementing a specific key combination that removes the command from the final recorded file. With this feature, we can …
enhancement
Checkpointing caching while replay the test
When we run a record file that uses blocks to validate that it works fine, it executes all commands. However, once we add some extra commands or fix the last one, we have to run the whole test again, which wastes significant time in most cases redoing the …
enhancement
From: https://gitlab.com/manticoresearch/clt/-/issues/5 While doing a scenario to test mysqldump with combined tasks no mcl, mcl only, mcl id with json, MVA, text fields, we found that it's a good idea to have the possibility to support dynamic variables …
Reusable blocks in the interactive mode
From: https://gitlab.com/manticoresearch/clt/-/issues/10 We now have support for reusable blocks, but we should also incorporate this feature into interactive mode. The task involves: Contemplating possible implementation methods. As proposed, we could …
UI to continously compose and run test
We should implement a simple UI that will perform the following functions: Expose an interface allowing users to enter commands for execution and display two rows of compared output - one modifiable and another from replay Automatically rerun tests when …
enhancement
Remove escape sequences from outputs
We should remove all bash sequences from generated output before we write it to the rep file to make it easier and more natural to compare outputs with different IDEs that may not render them or simply do not display them.
est::size_S
Skip adding succeed tests to summary
We should add to summary only those tests that failed same we do in comments
Description: HTTP requests sent through Buddy without ; echo at the end cause the request to hang indefinitely, and the test does not complete. The query works correctly when executed via MySQL CLI (mysql -h0 -P9306 -e "show version;"). The issue occurs …
bug
Extra pipe for all output from commands that we run
We should consider looking into the possibility of adding an extra pipe (e.g., > &3) that would allow us to store launched commands' output and review or retrieve it at the end of the test for debugging purposes. Also, as previously considered, it would …
Let's add support for ---comment--- totally ignored by CLT when replaying the test. It will make it much easier to understand what the author means when testing something.
Fix issue with cmp tool when comparing line with empy one
We have the rare case that while comparing outputs from record and replay it does not return error code
Investigate and fix incorrect CLT test validation
…➜ clt git:(main) ✗ ./clt test -t ./tests/centos:8_20231111_165817.rec -d centos:8; echo $? Replaying data from the file: ./tests/centos:8_20231111_165817.rec The replay result will be stored to the file: ./tests/centos:8_20231111_165817.rep ––– input ––– …
bug
Make CLT to run from global PATH
Currently when we add path to CLT in PATH we are still unable to use it due to failed to find required files to run in specified path
Adding a "--pause-on-fail" option to the CLI could be a great idea. It would keep the container running and allow us to jump in and debug cases involving race conditions.
Issue with wrong rec generated in manual mode
We have issue with recording in manual mode as follows: ./clt record -t test.rec load ––– input ––– echo 1 > /dev/null ––– output ––– - clt> ––– input ––– sleep 1 ––– output –––
Refactor: Deprecate PTY and use fork
Currently, we use PTY to read low-level data and try to understand if commands have finished or not due to the original idea of supporting interactive mode. We are moving forward and probably will not need it. To make the tool simpler and more error-proof …
The way to accept rep inside tested rec
We need a way to run a command after tests are launched. This command should show the difference between expected and actual results and allow us to accept the changes and modify the input recording file automatically. Here's the situation: We update …
enhancement
Currently, we check the output of each command with strict matching and regular expressions, which means all output needs to match exactly for each command. The idea is to introduce custom checkers/validators that can be represented as linked aliases or …