Tests & QA21 categories
Review these tests
A suite you inherited and do not yet trust.
Mediumreview
Review the tests below. Flag any that would still pass if the code were broken, any that assert implementation detail, and any that duplicate each other. Then name the one missing test I would most regret not having. Quote lines rather than describing them. 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.
Reviewing existing tests. Judging naming, mocking, and whether a test asserts behaviour or just the implementation.
Related prompts
Rename these tests so failures explain themselvesWhen a red CI run tells you `test_handler_2` failed and nothing more.Review my mocking strategyA test file with more setup than assertions.Would this catch a real bug?A test you wrote mainly to make coverage go up.Name this test properlyA failure message that tells you nothing about what broke.Behaviour or implementation?A test that breaks every time you refactor.One-line test descriptionA test whose intent is not obvious from its body.
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