Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

The process should fail if no tests were found #48

Open
MaxGenash opened this issue Jun 24, 2022 · 0 comments
Open

The process should fail if no tests were found #48

MaxGenash opened this issue Jun 24, 2022 · 0 comments

Comments

@MaxGenash
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant