You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
By default, jest fails if no tests were found. But when we use runner: 'groups' the process exits with status 0 which is unexpected and may lead to situations when we don't notice that something doesn't work, e.g. like #42 :
> test() { jest --group=$1 --verbose=false --runInBand --logHeapUsage --detectOpenHandles; }; test "unit"
Test Suites: 0 of 74 total
Tests: 0 total
Snapshots: 0 total
Time: 0.179 s, estimated 576 s
Ran all test suites.
Process finished with exit code 0
The problem is reproducible in jest-runner-groups v2.2.0 and Node.js v14.18.2
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
By default, jest fails if no tests were found. But when we use
runner: 'groups'
the process exits with status 0 which is unexpected and may lead to situations when we don't notice that something doesn't work, e.g. like #42 :The problem is reproducible in jest-runner-groups v2.2.0 and Node.js v14.18.2
The text was updated successfully, but these errors were encountered: