Google Play gives you three pre-production testing tracks — internal, closed, and open. They differ in tester limits, approval friction, and which one unlocks production access. Here's how to pick the right one.
Internal testing
The fastest track, for up to 100 internal testers. Builds go live almost instantly with no review delay — ideal for your own team and quick QA. It does not, on its own, satisfy the closed-testing requirement that new personal accounts must complete before production.
Closed testing
A controlled test with a defined group of testers (via email lists or Google Groups). This is the track that new personal developer accounts must use — running it with 12+ testers for 14 continuous days is what unlocks the ability to request production access.
Open testing
A public beta anyone can join from your store listing. Great for gathering feedback at scale before a full launch, but it exposes your unfinished app publicly and isn't necessary just to satisfy the production requirement.
Quick comparison
| Track | Testers | Best for | Counts toward production access? |
|---|---|---|---|
| Internal | Up to 100 | Team / quick QA | No |
| Closed | 12+ required | Meeting Google's requirement | Yes |
| Open | Unlimited | Public beta / scale feedback | Not required |
Which one do you need?
If you're a new personal developer account trying to publish, you need closed testing with 12+ testers for 14 days. Use internal testing alongside it for fast team QA, and consider open testing later if you want a broad public beta.
Run your closed test the easy way
AppTesterHub handles the closed-testing track for you — 12+ verified testers, 14 days, tracked end to end.
Start Closed TestingFrequently Asked Questions
What is the difference between closed and open testing on Google Play?
Closed testing is limited to a defined group of testers you invite (via email lists or Google Groups), while open testing is a public beta anyone can join from your store listing. New personal accounts must complete closed testing - not open - to unlock production.
Does internal testing count toward production access?
No. Internal testing (up to 100 testers) is for fast team QA and does not satisfy the requirement. You must run closed testing with at least 12 testers for 14 days to qualify for production access.
Which Google Play testing track do I need for production?
Closed testing. New personal developer accounts must run a closed test with 12+ testers for 14 continuous days before they can request production access.