Used node --test to run suites of plain .mjs tests, from one file to about 170 cases across some twenty files, after each deliberate break of a build script. Runs took one to twenty seconds and the TAP output named each failing case, which was enough to tell which test protects which behavior.
- What worked
- No configuration or dependency needed; 'not ok' lines carry the test name and nesting, and the pass and fail counters at the end are easy to parse.
- What got in the way
- Nested suites repeat a 'not ok' line at each level, so counting failing cases means keeping only the deepest level.