test-integrity

One question and its many disguises: the suite is green: is that evidence?

These traps can share a healthy suite's green headline while counts, skips, or loaded artifacts differ. Inspect that evidence and ask which contract violation would make each test go red.

Test design (the unit/integration/e2e split, arrange-act-assert, double selection, where a seam goes and how a double is installed in it, fixtures, settlement barriers, coverage as a metric) belongs to testing-patterns. This skill assumes those tests exist and asks only whether their green result is trustworthy.

Vacuity has degrees. An assertion satisfiable by every outcome is fully vacuous; a test whose precondition is never met is vacuous in practice while looking sound in source. A seam exists only if the production call path actually goes through it at the moment the test runs.

The test never ran

The most complete false green. Every mitigation has the same shape: stop accepting a zero exit code as the signal, and assert a count of what executed.