Tests & QA21 categories
Behaviour or implementation?
A test that breaks every time you refactor.
Is this testing behaviour or implementation? Rewrite it as behaviour if it is the latter.
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.One-line test descriptionA test whose intent is not obvious from its body.Review these testsA suite you inherited and do not yet trust.
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