Guide 7 of 7 · Updated October 2026
Internal vs closed vs open testing on Google Play — which track for what
Short answer: Internal testing is for you and your team (up to 100 addresses, no review, nothing in the Play Store); closed testing is the only track that counts toward Google's 12-testers requirement (email lists or Google Groups you attach, review for the first release, visible only to opted-in testers); open testing is a public beta anyone can join. A new personal account goes internal → closed (12 testers, 14 days) → production access → open testing or production.
Play Console gives you three testing tracks before production, and a new developer account has a reason to care which is which: only one of them counts toward the 12-testers requirement. Here is what each track is for, its limits, whether it goes through review, who can see it, and the order to use them in.
The three tracks side by side
| Internal testing | Closed testing | Open testing | |
|---|---|---|---|
| Who can join | Addresses you list (up to 100) | Email lists and/or Google Groups you attach | Anyone with the link; you can cap the number |
| App review before release | No — available within minutes | Yes, for the first release on the track (days) | Yes |
| Visible in the Play Store | No | Only to opted-in testers | Yes, as an early-access / beta listing |
| App content requirements | Minimal | Store listing and App content needed for review | Same as closed, plus the public listing |
| Counts toward the 12 testers | No | Yes — the only one | No |
| Best for | Checking the build yourself; QA; a team | The required test; a private beta with people you choose | A public beta after production access; scale testing |
Internal testing
Internal testing is the fastest track: you upload a bundle, add up to 100 email addresses, and the build is available to them within minutes with no review. Use it to check that the signed bundle installs and runs on real devices, to test in-app purchases with licence testers, and for your own team. Its opt-in link looks different (play.google.com/apps/internaltest/…) — testers who join through it are internal testers and do not count toward the 12. One build can be promoted from internal to closed later with "Promote release", which saves re-uploading.
Closed testing
Closed testing is a private release to people on lists you control: email lists you paste into Play Console, Google Groups whose members become testers automatically, or both. The first release on a closed track goes through Google's app review (plan for a few days), and the track has its own country list. The default closed track is called Alpha; you can create more tracks with different lists, for example one for a tester service and one for friends. Testers join through play.google.com/apps/testing/<package>, tap "Become a tester", and install from the Play Store like any app — the listing is just invisible to everyone else.
For a personal account created after November 13, 2023, this is the track the requirement lives on: 12 testers opted in for 14 continuous days, then the application for production access. The rule guide covers who it applies to and how the clock works; the opt-in link guide covers the mechanics.
Open testing
Open testing is a public beta: the app gets a Play Store listing marked as early access or beta, anyone can join from it or from a link, and you can cap the number of testers. Reviews written by open testers stay private to you, which makes it a good place to shake out problems before public ratings start. It goes through app review like a production release. For a new personal account it is not a substitute for the closed test — the requirement is specifically a closed test — and in practice open testing becomes useful once production access is granted, for a wider beta of each new version.
The path for a new personal account
- Internal testing — you and a couple of devices, same day. Check installs, sign-in, purchases, crashes.
- Closed testing — promote the build, roll out, wait for review, attach a list or group, share the opt-in link, reach 12 testers, run 14 days with feedback and at least one update. The day-by-day checklist.
- Apply for production access — from the app's dashboard, once the requirement card shows it. Up to 7 days for the answer.
- Production — create the production release (review again), then optionally keep an open testing track for betas of future versions.
Pitfalls that cost people weeks
- Collecting 12 testers on the internal track. The counter never moves. Move them to closed testing (they need to opt in again through the closed link).
- Creating the release but not rolling it out. "Saved" releases are invisible to testers; the opt-in page says the app is not available.
- Forgetting that the first closed release is reviewed. Upload it before you start recruiting, not after you have 12 people waiting.
- A second closed track with a fresh list in the hope of starting over: the requirement is per app, and the clock is per tester. Keep one track and keep the testers.
- Deleting the closed track after approval. You will want it for the next version's beta and for the next time Google asks for evidence of testing.
Short answers
Does internal testing count toward the 12-testers requirement?
No. The requirement for new personal developer accounts is measured on closed testing only. Internal testing is for up to 100 testers you add yourself, needs no review, and does not feed the requirement.
Does open testing count toward the 12 testers?
No. Open testing is a public beta anyone can join. Google requires the 12 testers to be opted in to a closed test for 14 continuous days.
Which track should a new developer use first?
Internal testing for yourself and your team to check the build, then closed testing with at least 12 testers for 14 days, then the production access application. Open testing is optional and comes after production access.