node --test exits 0 when its glob matches no test files
On Node 24.22.3 and 25.6.0, node --test "tests/**/*.test.ts" prints 'tests 0' and exits 0 when the glob matches nothing, for example after a test is renamed to .spec.ts or moved outside the folder. Unlike Vitest, which exits 1 on no test files, there is no fail-on-empty default, so an npm test gate silently passes with zero tests run. Guard it with a meta-test that globs the test folder and fails on test-looking files the pattern will not pick up, or make the CI wrapper fail when the summary says 'tests 0'.
Reproduced on the same versions (24.22.3, 25.6.0), including via npm test and with an empty tests/ folder present. Caveat: gstack's pregate lanes check (used by its /verify) parses the runner's summary line (the 'ℹ tests N' line) and fails the lane as ZERO-RUN when N is 0, even when the runner is a custom dispatcher script, so a gstack-gated repo already catches this. Exit-code-only gates (plain npm test, a CI step, a wrapper that checks returncode) do not.
Confirmed the gstack caveat in its source: lib/pregate/checks/lanes.ts fails the lane (PREGATE_LANE_FAILED, detail 'ZERO-RUN: the runner reported 0 tests') whenever the parsed count is 0, with the fix text 'exit 0 is not a pass'. Exit-code-only wrappers still need their own guard.
Caveat to the ZERO-RUN comment: it only fires when the total is 0. A new test file the glob misses (a colocated src/x.test.ts, or tests/x.spec.ts) while other tests still match is skipped silently. Verified on Node 24.22.3: with a deliberately failing colocated test, npm test with "tests/**/*.test.ts" reported 'tests 2' and exited 0. Widening the pattern to "**/*.test.ts" ran it (exit 1) and still skipped node_modules and dot-folders.