Closed DHFW closed 4 years ago
Thanks for providing the report. Can you please try:
Wallaby.js Start
command (not Wallaby.js Start Exclusive Test Run
command) to see if it helps?Wallaby.js Tests
VS Code output channel output?@ArtemGovorov, do you mean this:
0 failing tests, 4 passing (only executed src/services/invoices/invoices.service.test.ts) Launch Coverage & Test Explorer | Search Tests
0 failing tests, 4 passing (only executed src/services/invoices/invoices.service.test.ts) Launch Coverage & Test Explorer | Search Tests
Yes, thanks. Looks like the src/services/invoices/invoices.service.test.ts
is selected for exclusive run somehow. Have you tried to:
Wallaby.js Start
command (not Wallaby.js Start Exclusive Test Run
command) to see if it helps?Yes of course, I tried many different steps as mentioned including this. All without success. Can I hard reset something somewhere?
@DHFW In this case, it looks like Wallaby is selecting the file for an exclusive test run automatically based on its content. Can you please try to delete the whole content of the file (leaving maybe a single simple test), to see if it helps? If it does, please either share file content with us, so we could analyse it, or try adding things back to the file gradually to find out what's causing the tool to select the file for an exclusive test run?
@ArtemGovorov when I delete (or rename) the invoice.service.test.ts file, it does run all tests! But, when I restore the file, it only runs that file again. However, it seems after a few more trying that is works now... I don't know what it was or what helped... Thanks for the suggestions.
@DHFW - it's possible that your jest cache was corrupt. If you have the same problem in the future, please try the following:
npx jest --clearCache
.
I have 306 tests in my project (all run fine with Jest from command). I have played with the filtering tests feature but now I cannot run all tests again (no .only or .fit applicable). Jest runs them all.
Steps I tried:
Wallaby diagnostics report