Filter by reset
- Everywhere
173 - Issues
48 - Pull Requests
41 - Comments
84
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
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" …
CLT UI cosmetic touches and issues
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
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.
…"git operation failed": The button becomes invisible when I hover over it: Too much empty space here which makes the prompt's font too small: "your command or question" is confusing. It makes users wonder things like: "Is there a list of supported …
Proxy checkers dir inside container
We should think about the easiest way to integrate what we researched into the UI that is still in the branch. We should add a CLI binary that will utilize our MCP server and will be able to produce tests with user prompts through the UI and also allow us …
CLT UI fails to process %{NUMBER}
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 …
Bug: CLT crashes on test written with AI while it looks like correct
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 …
Add possibility to pass the directory required to run tests from outside
Compare only command output and improve diff logic
Add support of regex patterns through predefined file
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 …
Issue with wrong rec generated in manual mode
Do not post any info in case tests passed
Issue with wrong rec generated in manual mode
Skip adding succeed tests to summary
We should add to summary only those tests that failed same we do in comments
Skip adding succeed tests to summary
Block inside reusable block compilation
Skip adding succeed tests to summary
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 …
Skip adding succeed tests to summary