Quick answer
A good bug report has a short specific title, numbered steps to reproduce, what you expected and what actually happened, the device, OS and app version, how often it happens, and a screenshot or screen recording. Report one bug per report, and write it so someone who has never seen the problem can make it happen again.
Why the format matters
Developers can only fix what they can reproduce. A report saying "app not working" might take an hour of back-and-forth; a report with exact steps and a recording can be fixed in minutes. For testers, clear reports also get approved faster.
The seven parts of a bug report
| Part | Example |
|---|---|
| Title | Checkout: "Pay now" button does nothing after applying a coupon |
| Steps to reproduce | 1. Add any item to cart 2. Apply coupon SAVE10 3. Tap "Pay now" |
| Expected result | Payment screen opens |
| Actual result | Button greys out for a second; nothing happens |
| Environment | Redmi Note 12, Android 13, app v1.0.4, Jio 4G |
| Frequency | 3 out of 3 tries |
| Evidence | Screen recording attached |
Copy-ready template
Title: [Screen/feature]: [what goes wrong]
Steps: 1. … 2. … 3. …
Expected: …
Actual: …
Device / OS / app version / network: …
How often: … out of … tries
Evidence: screenshot or recording
Notes: anything else, such as "works if I remove the coupon"
Common mistakes
- Several bugs in one report — split them.
- Missing steps — "I was using the app and it crashed" can't be reproduced.
- Opinions instead of facts — "the design is bad" is feedback, not a bug. Report it separately as usability feedback.
- No version number — the bug may already be fixed.
- Screenshots with personal data — blur phone numbers, emails and payment details.
Bugs vs feedback
A bug is something that doesn't work as intended. Feedback is your opinion on how well something works. Both are valuable, but keep them apart so developers can prioritise. Our guide on useful user feedback covers the second kind, and businesses can learn how to ask for both in writing tester instructions.
Frequently asked questions
Should I report a bug I can't reproduce?
Yes, but say so clearly. Include everything you remember, the time it happened and any screenshot. Intermittent bugs are real and useful to know about.
What is severity?
How badly the bug affects users: a crash or payment failure is critical; a typo is minor. Some teams ask testers to suggest a severity.
Screenshot or video?
A screenshot shows a state; a short screen recording shows the steps. For anything involving taps or timing, a recording is better.