Filter by reset
- Everywhere
173 - Issues
48 - Pull Requests
41 - Comments
84
CLT UI cosmetic touches and issues
There are several issues that are not very critical but are great to address when we can: When we land with branch=.. we should reset the query string, because the branch has already switched, and reloading the page will reswitch it again. The "Create PR" …
I've got this test /home/box/clt/ui/workdir/sanikolaev/test/clt-tests/core/search-stats-global-vs-table-consistency.rec on the server and I can't run it via UI. It says "Running test" and never returns any status. Here's what it looks like after running …
CLT UI cosmetic touches and issues
CLT UI cosmetic touches and issues
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 …
CLT UI cosmetic touches and issues
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 …
CI: Display CLT Test EDIT link with a given domain as a parameter in action
Now with our UI, we can not just post error tests to comments in pull requests but also provide a link to edit it in the UI. The link looks like this: {UI_HOST}/?test_path=core%2Ftest-auto-schema.rec&branch=master&failed_tests[]=core%2Ftest-auto-schema. …
Currently, we keep Rust binaries in a repository that is not very efficient. We should think about introducing a CI pipeline that will build it, and as per CLT tool usage, we can just automatically download it when required to the local system and keep …
CLT UI fails to process %{NUMBER}
Closer integration with GitHub, so all changes are saved right away in a GitHub repo Support for Docker checkpoints Show progress while a test is running Syntax highlighting Add Docker image name as a comment (like metadata) Editable code blocks …
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
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 …
Bug: CLT crashes on test written with AI while it looks like correct
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.
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
Compare only command output and improve diff logic
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
Add support of regex patterns through predefined file
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
Issue with wrong rec generated in manual mode
Issue with wrong rec generated in manual mode
Skip adding succeed tests to summary
Skip adding succeed tests to summary
Skip adding succeed tests to summary