2026-10-26

Bug report template for closed test testers (copy and paste)

By the ClosedTest team

Testers often write "it crashed" or "the button doesn't work". You cannot fix that. A short, fixed format turns vague notes into findings you can reproduce. Google asks you to summarize the feedback you received and what you changed, so it pays to collect feedback in a form you can use. The requirement is on Google's testing requirements page.

The template (copy and send to your testers)

Bug report

1. What happened (one sentence): 2. Where in the app: (screen or feature name) 3. Steps to repeat it: 1. 2. 3. 4. What I expected: 5. What actually happened: 6. How often: every time / sometimes / once 7. My phone and Android version: (for example, Samsung A14, Android 14) 8. Screenshot or screen recording: (attach if you can)

Eight lines is enough. Do not add more, or fewer people will fill it in.

A filled example

This is invented, for a fictional note-taking app:

1. What happened: The Save button is partly hidden. 2. Where: Edit note screen. 3. Steps: 1. Open a note. 2. Tap Edit. 3. Look at the bottom right. 4. Expected: A Save button I can tap. 5. Actual: The button is behind the navigation bar. I can only tap the top half. 6. How often: Every time. 7. Phone: Samsung A14, Android 14. 8. Screenshot: attached.

Why each line is there

Line Why you need it
Steps to repeat If you cannot repeat it, you cannot fix it
Expected vs actual It shows whether the tester found a bug or a surprise
How often A problem that happens every time comes first
Phone and Android version Many bugs only appear on certain devices. See which Android versions testers use
Screenshot It saves a long description

What to do with the reports

  1. Copy each one into your feedback record, one row per finding.
  2. Mark how serious it is: High (crash, data loss), Medium (works wrongly or confuses), Low (cosmetic).
  3. Fix the High ones first and tell the tester. People who see their report fixed keep testing.
  4. Count the fixes. They are your answer to the form's question about what you changed. See the questionnaire guide.

Add it to your message

Paste the template into your message to testers, in the section on how to report problems.

ClosedTest is an independent service and is not affiliated with Google.

More guides

2026-10-26

Which Android versions do closed testers use? Data from ClosedTest's tester network

The Android versions used by ClosedTest's approved testers, why older versions matter for your app, and how to choose what to test.

2026-10-26

Testers cannot join your Google Play closed test: what to check

A tester says the app is not available or the link does not work? Check these causes in order. Most are fixed in minutes.

2026-10-26

Tester swap groups and r/AndroidClosedTesting: how they work and where they fall short

How developers swap tests to reach 12 testers, what to expect from communities and credit apps, and how to make a swap work.

All guides →