Closed Testing for Mobile Games: A 14-Day Playbook
Run a Google Play closed test for a game: tester tasks by day, what to measure (return rate, crashes, performance), and testing IAP and ads safely.
Short answer
Plan the 14 days around the player journey: tutorial and first session (days 1-3), core loop and progression (4-8), store, ads and edge cases (9-12), re-test fixes (13-14). Measure day-1 and day-7 return, crashes and frame rate on low-end phones, and use license testers and test ads so nobody is charged or flagged.
Why games need their own plan
Games live or die on the first session and on whether players come back. A closed test is your first real look at both. It’s also how you meet the same 12-tester, 14-day requirement as any app (see do games need the closed test).
14-day task plan
| Days | Tester task | You measure |
|---|---|---|
| 1-3 | Finish the tutorial, play 10-15 min | Tutorial drop-off, first-session crashes |
| 4-8 | Play daily, reach level X or rank Y | Day-1/day-7 return, difficulty spikes |
| 9-12 | Try the shop, rewarded ads, settings, offline | IAP flow, ad behaviour, edge cases |
| 13-14 | Re-test fixed issues, overall opinion | Stability of the final build |
Measure the right things
- Return rate: of testers who played on day 1, how many came back later? With 15-20 testers, read it as a signal, not a statistic.
- Where they quit: log level starts and finishes anonymously.
- Performance: frame rate and heat on a low-end device. Ask testers for their phone model.
- Stability: Android vitals and a crash reporter.
Money: test safely
- In-app purchases: add testers as license testers so purchases use test cards.
- Ads: use your ad network’s test ads or test device settings. Testers clicking live ads can get your ad account flagged.
- Loot boxes or random items: disclose odds where required, and answer the content rating honestly.
Writing it up
For the production access form, describe progression data (“14 of 18 testers finished the tutorial; we shortened it after 5 got stuck on step 3”), crashes fixed, and balance changes. Engine setup: Unity, Godot.
Frequently asked questions
Should game testers get unlimited currency?
A debug unlock helps testers reach later levels quickly, but keep at least some testers on the normal economy to judge balance.
How do I collect performance data?
Ask testers for their phone model and watch Android vitals. Add simple frame-time logging if you need more.
Can I test multiplayer with 12 people?
Schedule a short play session so testers overlap. Otherwise matchmaking can look empty.
Sources and how we keep this accurate
- Play Console Help: App testing requirements for new personal developer accounts
- Android Developers: Test your Google Play Billing Library integration
- Android Developers: Android vitals
Policy facts are checked against Google's own documentation on the date shown above. Google can change requirements at any time, so confirm in your Play Console. Where we give advice or estimates rather than Google's rules, we say so. TestersZone is independent and not affiliated with Google. Drafts are AI-assisted and reviewed by our team.
Need 12 testers? Get them free.
Test 3 apps, earn 60 credits, and list your app for up to 20 real testers with verified daily check-ins.
Start freeKeep reading
Do Games Need the 12-Tester Closed Test Too?
How to Publish a Unity Game on Google Play
How to Test In-App Purchases With License Testers
How to Create a Google Play Developer Account (2026)
Play Console Identity Verification Problems: How to Fix Them
How to Triage Tester Feedback in a 14-Day Closed Test
Browse all guides, or see the quick answers, guides and comparisons.