node-testing
Builds unit and integration test infrastructure for Node/TS/React - Vitest or node:test with explicit config, Jest-to-Vitest migration, v8 coverage gates that fail CI, React Testing Library, mocking discipline, flaky-test triage. Use when the user asks to set up tests, add coverage thresholds, pick a test runner, or fix a flaky setup. Not for E2E browser suites, lint rules, or CI workflows.
How do I install this agent skill?
npx skills add https://github.com/paldom/node-skills --skill node-testingIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a standard development tool for setting up and optimizing testing workflows in Node.js, TypeScript, and React. It uses well-known, trusted libraries and follows industry best practices for mocking and coverage. No security issues were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
node-testing
Builds test infrastructure where green means something: explicit runner config, coverage that fails the build instead of decorating it, and mocks that don't lie. The failures this skill fixes: models default to legacy Jest setups, write coverage reports nobody gates on, and stretch component tests into flaky pseudo-E2E.
When NOT to use
- E2E / real-browser flows → out of this repo's scope; route to Playwright and its docs (explicit non-goal).
- Lint →
node-lint; tsconfig →node-typescript. - Wiring jobs/matrices in GitHub Actions →
node-ci(this skill defines what to run; that one defines where).
Workflow
- Pick the runner by the decision table in
references/testing-playbook.md:- Vitest for anything non-trivial: TS/JSX native, watch UX, snapshots, mocking surface, React work.
- node:test for dependency-free pure-Node libraries where zero dependencies is itself the feature — with its trade-offs stated (loader for TS, weaker watch/snapshot ergonomics).
- Modernizing from Jest → Vitest is the default path (API-compatible for most suites); playbook has the migration steps.
- Write explicit config (no version-default reliance): environment
(
node/jsdom/ browser mode with tradeoff), globals policy, setup files. - Coverage as a gate: v8 provider with explicit
thresholdsthat fail the run. Philosophy: coverage finds gaps, it doesn't prove quality — prefer PR-delta discipline over chasing a global vanity number; never raise thresholds to force shallow tests. - React: React Testing Library + user-event on Vitest; test behavior via roles/text, not implementation details; real components from the repo in examples, never toys.
- Mocking discipline: mock at boundaries (network, clock, fs), not internal modules; fake timers come with the pitfalls list in the playbook.
- Verify: full suite green locally, coverage gate demonstrably fails when a
threshold is unmet (prove it once), scripts wired (
test,test:coverage).
Output spec
Runner chosen with written rationale; explicit committed config; coverage thresholds that fail CI; at least one real test demonstrating the setup (rendering a real component / exercising a real module); scripts wired; flaky triage checklist applied when that was the complaint.
Gotchas
- v8 coverage with AST remapping matches istanbul-level accuracy on modern Vitest — version-gate this and re-verify on major bumps.
- jsdom is not a browser: anything relying on real layout, navigation, or workers belongs in Playwright, not a heavier unit-test mock.
vi.mockhoists — factory functions referencing outer variables break silently; playbook shows the safe patterns.- A passing suite after
--changedfiltering is not a green suite — full runs gate merges (where:node-ci).
Files
references/testing-playbook.md— runner decision table, explicit configs, coverage gating, RTL patterns, mocking pitfalls, flaky triage.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/paldom/node-skills/node-testing">View node-testing on skillZs</a>