Auditing Test Quality

Vanity tests are tests that only assert mocks were called without validating actual behavior. Run the audit script to detect non-behavioral test names, excessive mocks, and poor mock-to-assertion ratios that indicate vanity tests masking low test quality.

Use an automated audit script (scripts/audit_tests.py or make audit-tests) that counts mocks and assertions, identifies non-behavioral naming, and reports issues with severity levels and remediation guidance for systematic improvement.

Yes. This Skill provides pre-commit hook and CI workflow configurations that enforce test quality standards continuously, catching vanity tests and poor mock-to-assertion ratios before code merges.

The audit prioritizes issues by severity. Focus on high-priority tests first by converting mock-heavy assertions into behavioral validations that test actual outcomes rather than just call verification.

Yes. The audit applies to unit and integration tests in projects using behavioral naming conventions and mock/assertion counting practices, surfacing quality issues across both test types.

Your project must have a test audit script, tooling to count mocks and assertions, behavioral naming conventions in place, and a standardized output format to report issues and remediation paths.