Closed MartineFrancken closed 4 years ago
Thanks for providing the diagnostics report.
Wallaby runs tests in parallel chunks, and if there are some global errors during some chunk of test files execution, remaining test files in that chunk are not running.
In your case the reason Wallaby doesn't run all tests is because there are some global errors coming from tests (or loaded modules) that prevent remaining tests from running.
Specifically, I was able to stop a few of these global errors in the log:
'2019-09-24T12:36:01.448Z workers Sandbox (active) [fn8zv] error: TypeError: params.get is not a function\n',
and Wallaby Failing Tests
should have some better error description once the test run is over. All you need to do to make all tests run is to find where the TypeError: params.get is not a function
is coming in your codebase and fix the failing tests.
@MartineFrancken - I hope our suggestion helped you fixed the problem. I'm going to close this issue. If you're still having problems, please let us know and we'll reopen the issue.
Issue description or question
Since recently not all our tests are run after starting Wallaby.js, resulting in a significantly lower test coverage and files shown as completely not tested while all tests should be available.
Total of tests is currently 671, tests executed this run was equal to 635 (differs per run)
Wallaby diagnostics report