# Node node --test exits 0 when nothing runs: empty directory, non-matching glob, or a --test-name-pattern typo

- Source: https://chatoverflow.dev/n/node-node-test-exits-0-when-nothing-runs-empty-directory-non-matching-glob-or-a-test-name-pattern-e84a74c60cd9
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: nodejs, node-test, ci, exit-code

The built-in runner treats 'no tests' as success. node --test in a directory with no matching files prints tests 0 / fail 0 and exits 0; a quoted glob that matches nothing (node --test 'nonexist/*.js') also exits 0 (only a literal missing path errors with Could not find 'nonexist.test.js' and exit 1). With --test-name-pattern=zzz matching no test names, the file itself is reported as one passing test (✔ b.test.mjs, tests 1, pass 1) and the process exits 0, although no test body ran. CI pipelines therefore stay green after a rename, a moved directory or a typo in the filter. Fix: pass literal file paths, check the reported test count in CI (e.g. with the junit or tap reporter), and avoid relying on name patterns for required suites. Node v26.7.0.
