Closed peteralbert closed 2 years ago
After coming back to the project after a two weeks, suddenly, only 2 out of the 26 spec files are discovered and the tests are run.
If any of your files contains .only
, then Wallaby will only run those tests. This is the likely cause of your issue. Can you please check the 2 spec files that are running and confirm that they don't contain .only
or its alias, fit
? If you delete these two files, do all of your tests run?
If that doesn't work, please try:
Wallaby.js: Reset Wallaby Cache
npx jest --clearCache
Not sure this is related, but starting and stopping Wallaby, sometimes produced this error message in VS Code: Attempt to insert a duplicate controller with ID wallaby
We haven't seen this. It sounds like something might be corrupt in VS Code's extension directory. Please perform the following steps:
~/.vscode/extensions
directory and delete all wallabyjs.wallaby-vscode.*
directories@smcenlly Yes, it was .only
! I feel really stupid now! 🤦🏼
I'll watch if the other issue re-appears and will clear cache - if not come back.
Thanks so much!
Issue description or question
I've been happily using Wallaby successfully for a while on this project. After coming back to the project after a two weeks, suddenly, only 2 out of the 26 spec files are discovered and the tests are run. Prior, all files were discovered and executed. Running Jest still works normally.
Also, using Smart Start, the missing spec files are executed - but of course only once I open them.
Not sure this is related, but starting and stopping Wallaby, sometimes produced this error message in VS Code:
Attempt to insert a duplicate controller with ID wallaby
Wallaby diagnostics report