Closed fvanwijk closed 2 years ago
Same here, and not sure that it's related to automatic config. I added
tests: [
'test/**/*.test.ts'
],
to my wallaby.js and selected that configuration - still running tests in node_modules.
(this just started after I went back to automatic updates and got the latest version, after #3041)
Thanks for reporting the problem, this has been fixed in the latest version of Wallaby, v1.0.1317
.
I have updated the core. I can verify that the tests in node_modules are now ignored. Thanks for the quick fix. Any pointers what causes the issue?
You see "0 failing tests, 1 passing" instead of "0 failing tests, 1 passing, 17 todo". However the test is still passing, while it is failing with Vitest.
Or could this be related to (unexpected behavior in) unplugin-vue-components in combination with vanilla vite, and is the bug not triggered when running via Wallaby?
Any pointers what causes the issue?
The problem in Wallaby was caused by a recently introduced bug.
If I understand the rest of your comment properly - you have the same problem when running tests using vitest
from the CLI? Perhaps try updating your test matching pattern to ignore node_modules
in your vitest
configuration?
Issue description or question
I'm trying to make Wallaby work with an example project to demonstrate a different issue. The automatic configuration results in a passing test, however it also tries to run tests in node_modules.
You see
0 failing tests, 1 passing, 17 todo
. The 17 tests are in node_modules/cssstyle/lb/parsers_test.js.The Wallaby console outputs:
Also note that my test passes in Wallaby, but I expect it to fail (run
npm test
to see). Maybe the vite.config.ts is overridden by Wallaby somehow?Wallaby diagnostics report