Verified:GitHub

node-test-discovery

Validates node --test invocations so test paths resolve to real files instead of silently running zero tests.

Updated Jun 12, 2026

Search Tags:#testing #github actions #package.json #ci #node #test discovery #node --test

One-click install

npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill node-test-discovery-missingbulb

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: node-test-discovery
Source: https://github.com/missingbulb/GoogleCalendarEventCreator/tree/main/.claudinite/shared/packs/node/skills/node-test-discovery
Command: npx skills add https://github.com/missingbulb/GoogleCalendarEventCreator --skill node-test-discovery-missingbulb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Node's built-in test runner skips dot-directories during discovery and exits green when it finds no tests, so a misconfigured CI step or package.json script can report success while running nothing at all. ## Core Features & Use Cases - Silent-failure detection: Explains why a bare `node --test` invocation over a suite in a dot-directory runs zero tests and still passes. - Path resolution checks: Ensures every path or glob passed to `node --test` actually matches files in the tree, catching typos, moved fixtures, and renamed directories. - Use Case: When editing a GitHub Actions workflow or a package.json test script, verify the test command by confirming the reported test count is non-zero rather than trusting a green exit code. ## Quick Start Ask the assistant to review your workflow or package.json test script and confirm the node --test invocation actually discovers and runs your test files.

Frequently Asked Questions about node-test-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does node --test pass without running any tests?▼

Node's test runner skips dot-directories during default discovery, and finding no tests is treated as success. A suite living under a hidden directory produces a green run with zero tests executed.

How do I run node --test on tests in a dot-directory?▼

Pass the path or an explicit glob as an argument to node --test, since default discovery ignores hidden directories. Then confirm the run reports a non-zero test count to prove files were found.

How do I verify a Node test script in CI actually runs tests?▼

Watch the reported test count and assert it is non-zero rather than relying on the exit code. A typo'd glob, moved fixture, or renamed directory produces the same zero-test green result as a passing suite.

Does a green node --test exit code mean my tests passed?▼

Not necessarily. Node exits successfully when discovery finds nothing, so a green run can mean zero tests executed. The reliable property to check is that the test count is non-zero and named paths resolve to existing files.