Defect report: one you can reproduce
level 1 · 15 min · defect report
A failing test is only useful if someone fixes the defect. For that, whoever fixes it needs to reproduce the problem and know what was expected. A vague report sends the conversation back to the tester, and the defect waits.
A good report answers six questions: what the defect is, how to reproduce it, what was expected and why, what happened, where it happened and what the impact is. Each part needs facts, not adjectives.
Rule of thumb. Write for someone who was not there: a title that describes the defect, steps with the exact values, the expected result with the rule that justifies it, the actual result, the environment and the real impact.
Read a weak report
This report reached the team after a shipping test failed. Try to reproduce the problem with it alone.
Wrong shipping
Shipping is wrong. It does not work right, I think it is a bug. Urgent!!!
Questions to ask it
- Can you reproduce the problem from this text alone?
- Can you tell what the expected result was and what was actually obtained?
- Does the reader know the version and environment where it happened?
- Does the title describe the defect or just point at an area?
Exercise: build the report
The defect: an order of exactly $100.00 pays shipping, but the rule says orders of $100.00 or more ship free. Choose the best version of each part.
Choose a version for each part.