Tests & QA21 categories
Write a regression test from a bug report
A bug is fixed and you want it to stay fixed.
Longregressionbugtest-cases
Write a regression test for the bug below. 1. State the exact behaviour the test must lock in, in one sentence. 2. Identify the minimum setup needed to reproduce it. Strip anything incidental from the original report. 3. Write the test. It must fail against the old code and pass against the fix. Say which line would have failed before. 4. Name the class of bug this belongs to, and suggest one or two neighbouring tests covering the same class, since bugs like this rarely occur alone. 5. Say where the test belongs: unit, integration, or end to end, and why that level is the one that would have caught it. If the bug report lacks the detail needed to reproduce it, list the specific questions to ask rather than guessing. Bug report: The fix:
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.
Failing and flaky tests. Diagnosing a red run, stabilising a flake, and locking a fixed bug in with a regression test.
Related prompts
Make this flaky test deterministicA test that passes locally and fails in CI roughly one run in ten.Diagnose why this test is failingA red test where the failure output does not point anywhere obvious.Why is this flaky?A test that fails once every twenty runs.Write the failing case firstA bug you are about to fix.Regression test from this bugA bug you have just fixed and never want back.Diagnose this failing testA red test with an unhelpful failure output.
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