AppReviewX Log in

Test report template for beta tests

Summarize what was tested, what was found and what was decided, in one page.

updated ·2 min read

In this guide

A test report ends a test round. It answers three questions for whoever decides about the release (often you): what was tested, what was found, what happens next. Keep it to one page. If it needs more, link to your bug list.

Template (copy and paste)

TEST REPORT: <app name> <version / build>
Period: <from - to>     Author: <name>

1. SUMMARY (3 lines max)
   Recommendation: <GO / GO with known issues / NO-GO>
   Why: <one sentence>

2. WHAT WAS TESTED
   Scope:    <features and flows covered>
   Not tested: <what was left out, and why>
   Devices / OS: <list>
   Testers:  <number and kind, e.g. 8 developer peers>

3. RESULTS
   Test cases run: <n>   Passed: <n>   Failed: <n>   Blocked: <n>
   Feedback items received: <n>

4. FINDINGS
   | # | Severity | Area | Summary | Status (open / fixed / won't fix) | Link |
   |---|----------|------|---------|-----------------------------------|------|
   | 1 |          |      |         |                                   |      |

5. KNOWN ISSUES SHIPPING WITH THIS BUILD
   - <issue, workaround if any>

6. WHAT TESTERS LIKED / CONFUSED THEM
   - Liked:    <short>
   - Confused: <short>

7. DECISIONS AND NEXT STEPS
   | Action | Owner | Due |
   |--------|-------|-----|
   |        |       |     |

8. OPEN QUESTIONS
   - <question>

Example (illustrative, invented numbers)

TEST REPORT: Example Recipe App 2.1 (build 214)
Period: 2026-11-03 - 2026-11-09     Author: Sam

1. SUMMARY
   Recommendation: GO with known issues
   Why: No crashes in the core flow; two cosmetic issues remain.

2. WHAT WAS TESTED
   Scope: sign-up, search, save recipe, offline reading
   Not tested: dark mode on tablets (not supported)
   Devices / OS: two phones, Android 11 and 14
   Testers: 6 testers from a peer group

3. RESULTS
   Test cases run: 20   Passed: 17   Failed: 2   Blocked: 1

4. FINDINGS
   | 1 | High   | Search  | Empty query shows blank screen | fixed      | #12 |
   | 2 | Low    | Profile | Avatar cropped on small phones | won't fix  | #15 |

7. DECISIONS AND NEXT STEPS
   | Retest search fix | Sam | 2026-11-10 |

How to adapt it

  • Lead with the decision. Readers who stop after section 1 should still know what to do.
  • Use a severity scale you defined beforehand. See the bug severity and priority matrix.
  • Only report numbers you counted. Leave a field out rather than guessing.
  • Google Play closed tests: note the number of testers and the test period so you can see later what the round covered. Do not copy requirement figures from memory; see closed testing with 12 testers and the current official policy.
  • Share with testers? Remove private details and tester names before you do.

Start free to collect private, structured feedback for your next report.