-
-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "Turn on continous run" option to the right click menu #451
Comments
VSCode doesn't provide enough API to sync the test run request and the state of the "continues" run button in the test tree. I found some undocumented commands but they use private test item implementations that I don't have access to:
There are already issues in the vscode repo, I recommend you leave a comment there: microsoft/vscode#188305 and here: microsoft/vscode#210848 |
I'd actually like something similar. When I purposefully failed a test, I had to manually rerun it. When I fixed the test (for demonstration purposes), I had to rerun it again. What if instead of all that, if you notice there's a test, have a preference in VSCode that allows it to automatically rerun that one test or the whole file. Either way, it'd be nice if it was watching for changes to files when I was working in them and specifically when I was saving the file. Even better is if I could have it run after a debounce on typing. May or may not be good for that one. VSCode errors are annoying when it does that while I'm typing :/. |
Use Continuous run when working on tests: https://github.com/vitest-dev/vscode?tab=readme-ov-file#in-the-testing-view
If your VSCode saves files on type, then Vitest will run those tests after they are saved on the file system when you use Continuous run. |
Clear and concise description of the problem
I wish to be able to quickly enable continous run mode (watch mode) without having to open the test panel, search for the right test in the long list, and click on the eye icon.
I know i can click "reveal in test explorer", but a shortcut would be even nicer.
Suggested solution
I would love to just right click on the test run icon and click "run continously"
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: