-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Vitest extension doesn't rerun tests when test files change #483
Comments
Confirmed. I think this is related to #472 which was probably closed in error. |
just tried the latest release 1.2.13. Same thing. And there is no coverage report also. |
I don't know if it's the root cause, but Line 142 in e0ea185
|
My entire team has downgraded to version 1.2.6 to work around this issue. It has its own issues, but better than having to click the refresh button in test explorer after every little change to a test file or SUT file. |
i will add my voice here, its clearly an issue and having to reload at every change is not the most ideal thing.. |
Cannot reproduce with the reproduction you've provided. Note that you didn't fill the issue template correctly since the "Output" is empty. |
Hello @Igor-Vuk. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with |
This should be fixed by 6e2f2c4 |
In 1.2.15 I added some logs in the watcher if |
I have 1.4.4 installed and this still happens. Everytime I had a new test to a test file I ran previously it doesn't recognize the test is there I have to reload in order for extension to recognize new test. |
We've had issues like this for ages. But I don't want to report it because there's no way I can make a repro, and so it'll just be closed. Our developers have to reload VS Code like 10 times a day. We are in the process of trying to switch to another test extension, but others are unstable too. We hope switching to Deno 2.0 will help, or perhaps even Bun when they finish their extension. I hope someone finds a root cause. I wonder how many are secretly having this issue. |
Refresh tests doesn't work for us. It simply doesn't do anything. It does at first, but not after you've either run a test once or debugged a test once. I'll try the debug option you provided to see if I can share more details. |
The refresh button calls |
1.6.0 adds an option I wasn't able to reproduce the hanging "refresh tests" button yet even when there is an infinite loop in the test file 🤔 |
This issue is affecting me using version 1.6.0. "Refresh tests" works for me, but it takes a while since there are many tests in our repo. "Continuous Run" does not work. If it helps, I'm in a pnpm monorepo, but the tests that I'm trying to use this extension for are all contained to one package (i.e. the test files and the code I am testing are all in the same package, and I'm trying to trigger a re-run by editing code in that same package). I'll see if I can post a minimal repro later today. |
for me,
watching, but not refresh the test when toggling the line
|
If you have issues with this, I recommend enabling |
all output are these lines
|
Describe the bug
When test files change, Vitests extension doesn't rerun them. The only way to rerun tests files and get new data is to click "Refresh tests" and then "Run tests" on every change inside test files. In terminal tests are rerunning normally on files save. I uploaded a short video
tests.mp4
Reproduction
Write any type of tests and run them
Output
.
Version
1.2.12 published 2024-09-30
Validations
The text was updated successfully, but these errors were encountered: