Bug report template for app testers (copy and paste)
Testers describe what they felt; you need what they did. A fixed template turns "it crashes sometimes" into something you can reproduce in five minutes.
The template
Title: one line, what is wrong and where
Steps:
1. ...
2. ...
3. ...
Expected: what should have happened
Actual: what happened instead
Frequency: always / sometimes (about how often)
Device and OS: e.g. Pixel 7, Android 14
App version or build: e.g. 1.4.2 (87)
Extra: screenshot, screen recording, or error text
Why each line matters
- Steps are the whole bug. If you cannot repeat them you cannot fix it.
- Expected and actual separate a bug from a taste difference.
- Frequency tells you whether you chase a race condition or a plain logic error.
- Device, OS and build save the first round of back-and-forth, and many bugs only appear on one vendor or Android version.
- A screen recording often shows the missing step that the tester forgot to write down.
Make testers use it
Paste the template into the test notes or the task description. Ask for one report per problem rather than a list in one message, so each can be tracked and closed. Thank people who follow the format; they are doing you a real favor.
Questions developers ask
Should testers also suggest fixes? Welcome, but separate it from the report. A bug report states facts; a suggestion goes under Extra.
What about vague reports? Reply with the template and ask for the missing lines. Most testers fill it in gladly. See also how to write feedback a developer can act on.
Need testers for your app? Open a test group on AppReviewX. Start free