Test Suite Quality Audit
Assess coverage meaning and test reliability.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Audit my test suite and score what it really protects. Language and test framework: [LANGUAGE_AND_FRAMEWORK]. Test output summary (number of tests, failures, run time, flaky tests): [TEST_SUMMARY]. Sample tests (a few good-looking, a few doubtful): [PASTE_SAMPLE_TESTS]. Coverage report if available: [COVERAGE_SUMMARY]. Score each dimension from 1 to 5 with evidence quoted from the samples: 1. Meaningful assertions (tests that check behavior rather than only running code). 2. Failure messages that explain what broke. 3. Isolation and independence of tests. 4. Flakiness and determinism (time, randomness, network, shared state). 5. Speed and feedback time. 6. Coverage of risk: critical paths, edge cases, error handling, security rules. 7. Readability and naming. 8. Balance across unit, integration, and end-to-end tests. 9. Test data management. 10. Maintenance cost when code changes. Show the total and the three weakest dimensions. Then name five tests to delete or rewrite, five missing tests that matter most, and a mutation-testing experiment I can run on one module to check if tests catch bugs. Explain why high coverage can be misleading.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.