The card below is the “product under test”. Use guided mode to see the bug list upfront, or blind mode to find them yourself first.
Techniques: Defect analysis, Metrics & reporting
Bug report: BUG-2201
| Title | The app is broken |
| Reporter | Sarah M. (Stakeholder) |
| Environment | My computer |
| Steps to reproduce | I tried to use it and it didn’t work. |
| Expected | It should work |
| Actual | It doesn’t work |
| Severity | Critical |
| Evidence | None attached |
| Status | Assigned to dev lead for immediate fix |
Your findings
0 / 0 bugs foundTick each bug as you confirm it on the page above. Progress saves automatically.
Write down every bug you find. Be specific — where it is, what’s wrong, what it should be.
Planted bugs (5)
- A good bug title describes the specific symptom and location, e.g. 'Checkout fails with 500 error on Visa payment'. 'The app is broken' tells the developer nothing.
- Environment should include: OS, browser name+version, app version/build, and user role. 'My computer' is unreproducible.
- 'I tried to use it and it didn't work' cannot be followed by a developer. Steps must be numbered, specific, and reproducible.
- Critical severity requires clear justification — data loss, security breach, complete feature failure. Without evidence or specifics, the rating can't be validated.
- This report is missing enough information to be fixed. Assigning it immediately means the developer will waste time seeking clarification. It should be returned to the reporter for more information first.
Defect triage: ask — can a developer reproduce this from the steps? Is the severity justified? Is the environment specific enough? What evidence supports the claim? Return it for more info if any of these fail.