What you receive at the end of your closed test.
A closed test should leave you with evidence, not just a list of testers. This is a sample of the final report: the result, the findings with severity, what was expected and what actually happened, device coverage, and the facts you need for your Google production-access application.
This is a sample. It describes a fictional app ("Example Notes") and uses example numbers. Your real report has the same format, filled with your own app's data. We never publish a customer's results without their permission.
Executive Summary
Example Notes was stable throughout the 14-day test: no crashes, freezes or force-closes were reported by any tester. Testers used the note editor, folders, search, sync, settings and dark mode every day across 9 device models and 4 Android versions.
Three issues should be fixed before production, and five improvements are suggested. None of the issues blocks the core purpose of the app.
Result: PASS WITH ISSUES
Test Scope
- Duration: 14 days
- Testers: 16 (12 standard testers and 4 Pro testers)
- Devices: 9 models, Android 11 to 15
- Areas tested: onboarding, creating and editing notes, folders, search, sync, settings, dark mode, landscape mode
Findings
1. Save button partly hidden behind the navigation bar
Severity: High
Device: Samsung Galaxy A14, Android 14
What happened: In the note editor, the Save button sits under the system navigation bar. Only the upper half is visible, so it is easy to miss when tapping.
Expected: Primary actions stay fully visible and easy to tap.
Actual: About half of the button is covered.
Recommendation: Respect the system safe-area insets and test with both gesture navigation and 3-button navigation.
2. Search ignores accented characters
Severity: Medium
Device: Google Pixel 7, Android 15
What happened: A note titled "Café menu" is not found when searching for "cafe", and the other way around.
Expected: Search treats accented and plain letters as the same.
Actual: Notes with accents are missed.
Recommendation: Normalise text (for example with Unicode normalisation) before comparing.
3. Low text contrast in dark mode
Severity: Medium
Device: Xiaomi Redmi Note 12, Android 14
What happened: The grey hint text in the empty-folder screen is hard to read on the dark background.
Expected: Secondary text still meets a readable contrast level.
Actual: The hint text almost disappears.
Recommendation: Use a lighter grey in dark mode and check it against the WCAG contrast guidance.
Suggestions for Improvement
These are improvements, not confirmed bugs.
- Add a short first-launch guide that explains folders and sync.
- Show a confirmation before deleting a folder that contains notes.
- Let the user choose the default font size in settings.
- Add a count of notes next to each folder name.
- Make the sync status message more specific than "Syncing".
Positive Feedback
- Fast start-up on every tested device, including older models
- Clear and simple editor
- Sync worked reliably in every tester's report
- Dark mode is consistent apart from the contrast issue above
Limitations
- Most daily submissions were screenshots with a short note; the findings above come from the detailed notes of the Pro testers and the reviewed screenshots.
- The sync behaviour was checked on home and mobile networks, but not on a very slow connection.
Priority Recommendations
- Fix the Save button overlap with the navigation bar.
- Make search ignore accents.
- Improve dark-mode contrast for secondary text.
- Add the first-launch guide.
- Re-check these fixes in a short follow-up test before applying for production.
Final Testing Assessment
Result: PASS WITH ISSUES
The app is stable and its core flows work on all tested devices. Fix the three issues above and re-verify them before you submit your production-access application.
Google asks about your closed test, your app and your production readiness. For the questions about the test, your report shows what your test actually recorded (example numbers below).
Two answers are yours to write: what you changed because of what testers found, and how you decided your app is ready for production. The findings above are your starting point.
What every report contains
- ✓ The result (Pass, Pass with issues or Fail) and the number of findings by severity, at the top
- ✓ Each finding with its severity, the device it happened on, what was expected and what actually happened
- ✓ Suggestions for improvement, kept separate from confirmed issues
- ✓ What worked well, so you know what not to change
- ✓ Honest limitations: what the test could not cover
- ✓ Priority recommendations in the order you should fix them
- ✓ The facts about your test for Google's production-access application
Google makes the final production-access decision. A report like this documents your testing honestly; it does not guarantee approval.