Test Suite Audit
By Taylor Davis · Published · Updated
Audits a test suite for tests that cost more than they protect and for missing coverage that matters, reporting findings without changing any code.
Prompt template
## Test Suite Audit Audit my test suite and report; do not edit anything. - Project and language: [text: e.g. Python web API] - Test location and command: [text: Folder and run command] - Suite pain points: [textarea: Slow or flaky or hard to maintain tests] - Run time of the full suite: [text: Minutes] - Most critical user flows: [textarea: What must never break] - Report detail: [dropdown: Summary, Detailed] Read the tests and score each group on cost against protection. Cost signals: slow runtime, flakiness, heavy mocking that mirrors the implementation, duplicated setup, assertions on private details, and failures that need hours to diagnose. Protection signals: catches real regressions, checks behaviour rather than structure, covers a critical flow. List the tests that cost more than they protect and say whether to delete, merge, or rewrite each. Then map the critical flows to tests and name the gaps that matter: untested money paths, auth, data migrations, error handling. Rank gaps by the damage of a failure there, not by line coverage. Report only. Close with five actions in priority order and the estimated run time saved.