Tests & QA21 categories
Audit this suite for untested behaviour
You wrote tests and want to know what you did not think of.
Here is my code and my existing tests. Tell me what is untested. 1. List behaviours the code has that no test asserts. Quote the line of code for each. 2. List missing edge cases: boundaries, empty, null, maximum size, error paths, concurrency. 3. Point out any test that would still pass if the code were broken, and say exactly how you would break the code without failing it. 4. Identify tests that assert implementation detail rather than behaviour, and would fail on a harmless refactor. 5. Give me the five highest-value tests to add, as actual code in my framework. Rank by likelihood of catching a real future bug, not by coverage percentage. If the suite is genuinely adequate, say so. Code: Tests:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Finding coverage gaps. Working out which behaviours, edge cases and error paths nothing currently checks.
Related prompts
Write test cases from acceptance criteriaA story is ready for QA and the criteria need turning into concrete checks.Find property-based test ideasCode with a large input space where example tests only scratch it.Test the error pathsWhen every existing test exercises the happy path.Brainstorm edge cases for this featureBefore writing tests, to widen the input space you are imagining.What is untested here?Code with tests you suspect are not covering much.Fifteen edge cases, list onlyA function you are about to call finished.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser โ free