Quick answer: Google Play has three testing tracks: internal (up to 100 testers, available within minutes), closed (email lists or Google Groups) and open (anyone on Google Play). Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for the last 14 days in a row before they can apply for production access. Testers cannot leave public reviews, so capture crashes and bug reports in the game itself.
For many solo developers, the closed test is no longer optional: it is a gate to launching on Google Play at all. It is also a genuinely useful beta, if you set it up to collect more than silence. Here is how the tracks work, how to clear the 12-tester requirement, and how to come out of it with real bug reports.
The three testing tracks
| Track | Testers | How they join | Notes |
|---|---|---|---|
| Internal testing | Up to 100 | Email list and opt-in link | New builds reach testers within minutes; may not be subject to standard review |
| Closed testing | Email lists (up to 2,000 users each) or Google Groups | Opt-in link | The track that counts toward the 12-tester requirement |
| Open testing | Unlimited, or a cap of at least 1,000 | Anyone, from your store listing | A public beta |
Testers on any track cannot leave public reviews for test versions, and their feedback does not affect your public rating. Closed and open testers can send you private feedback through Google Play.
The 12 testers for 14 days requirement
If your personal developer account was created after November 13, 2023, you need a closed test with at least 12 testers who have been opted in for at least the last 14 days continuously before you can apply for production access. (The number was 20 until December 2024.) Practical tips:
- Recruit more than 12. Some testers opt out or never install. Aim for 20 or more so a few dropouts do not reset your clock.
- Use a Google Group so you can add testers without editing the track each time.
- Ask testers to actually play. Google asks about your testing when you apply, so a test with real engagement and feedback is much easier to describe.
- Ship updates during the test and fix what testers report; it is the point of the exercise.
Setting up a closed test
- Build an Android App Bundle (AAB) signed with your upload key.
- In Play Console, open Closed testing (under Testing), create or pick a track, and add testers by email list or Google Group.
- Create a release with your AAB and roll it out to the track. The first time, the opt-in link can take several hours to start working.
- Share the opt-in link. Testers accept, then install from Google Play as normal.
Getting real bug reports out of testers
Twelve to a few hundred testers on a range of Android devices is exactly where device-specific crashes show up, and exactly where nobody writes them down. Before you roll out the test build:
- Capture crashes and errors automatically with an in-game SDK, so a crash on a phone you do not own still reaches you with the stack trace, device, OS and build.
- Add a report button to the pause menu, with the screenshot and device attached automatically.
- Check Android vitals in Play Console too, for native crashes and ANRs reported by the system.
- Read logcat yourself for anything you can reproduce on your own device: see reading Unity Android crash logs with logcat.
Create a free Bugnet project and add the SDK for your engine before the test starts; crashes and in-game reports from every tester land in one list, grouped by bug. After launch, Bugnet can also turn Google Play reviews into bug reports. Testing on iOS at the same time? See how to run a TestFlight beta.
Frequently asked questions
What is the Google Play 12 testers requirement?
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for at least the last 14 days continuously before applying for production access.
What is the difference between internal and closed testing on Google Play?
Internal testing is for up to 100 testers, with builds available within minutes. Closed testing uses email lists or Google Groups, supports more testers, and is the track that counts toward the 12-tester requirement.
Can closed testers leave reviews on Google Play?
No. Testers cannot leave public reviews for test versions, but closed and open testers can send private feedback through Google Play.
How do I get crash reports from Google Play testers?
Check Android vitals in Play Console, and add an in-game SDK that captures crashes and errors automatically with the device, OS and build attached.
How long does it take for a closed test link to work?
The first time you publish a test, the opt-in link can take several hours to become available to testers.
Twelve testers is the minimum Google asks for. Twelve testers who report bugs is the useful version.