Filter by reset
- Everywhere
110 - Issues
30 - Pull Requests
23 - Comments
57
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
Make CLT to run from global PATH
It looks like it's possible and might be a good idea to add measurement of 'peak memory' and 'CPU time' usage after each command we run, similar to how we track 'duration'. To make this happen, we could try tracking the PID of the bash process we run and …
enhancementest::size_M
Make CLT to run from global PATH
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.
bug
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
bug
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
Skip adding succeed tests to summary
Add possibility to delay next command to replay
Skip adding succeed tests to summary
Add default delay a few ms between inputs
Sometimes, when you replay a CLT test, one input may run too soon after the previous one. It is recommended to add a default delay between inputs, such as 5ms.
Skip adding succeed tests to summary
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 …
Improve CLT output with user command
Add info to README about output MUST contain new line as a limitation
Improve CLT output with user command
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 …
Tests stucks if no next command passed
Tests stucks if no next command passed
Add possibility to pass the directory required to run tests from outside
Add default delay a few ms between inputs
Add default delay a few ms between inputs
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
Add default delay a few ms between inputs
Do not post any info in case tests passed
Remove escape sequences from outputs
est::size_S
Skip adding succeed tests to summary
We should add to summary only those tests that failed same we do in comments
Remove escape sequences from outputs
est::size_S
Compare only command output and improve diff logic
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
Add support of regex patterns through predefined file
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 –––
Tests stucks if no next command passed
I faced with this behavior in this test It is stuck if: kubectl get deployment my-helm-manticoresearch-balancer -o=jsonpath='{$.spec.template.spec.containers[:1].image}' And like this kubectl get deployment my-helm-manticoresearch-balancer -o=jsonpath …
est::size_S