Test Quality Verifier
Use this skill when you need to validate that tests are meaningful (not just truthy checks), cover important behaviors, and actually fail when the implementation is wrong.
Quick Use
- •If multi-agent is enabled, invoke
@test_quality_verifierand ask it to audit the current repo's tests and improve them as needed. - •If working solo, follow the workflow below.
Workflow
- •Identify the test runner and conventions (look for
package.json,pyproject.toml,go.mod,Makefile, CI workflows). - •Enumerate tests (
rg -n "describe\\(|it\\(|test\\(|def test_|func Test" .is a quick start). - •Find vague assertions:
- •JS/TS: lone
.toBeTruthy(),.toBeDefined()with no value/shape checks; literal==literal asserts. - •Python:
assert True,assert resultwith no comparison;passin tests. - •Go: tests that only check
err != niland never validate returned values.
- •JS/TS: lone
- •Run the repo’s existing test/coverage commands if present; otherwise use framework defaults.
- •Replace vague asserts with checks on actual values, shapes, and error paths. Add tests for uncovered branches.
- •Re-run tests/coverage and ensure the report reflects reality.
Output
Produce a report with:
- •Files scanned, vague assertions found/fixed, tests added
- •Coverage numbers if available (and where they came from)
- •PASS/FAIL with concrete reasons