Internal vs Closed vs Open Testing on Google Play: What's the Difference?
Play Console offers three testing tracks under the same "Testing" section, and it's a genuinely easy place to pick the wrong one — especially since only one of them satisfies the production access requirement most new developers are actually trying to clear.
Internal testing
Meant for your own team — up to 100 testers, instant availability with no review wait, no country restrictions to configure. It's built for quick iteration before you're ready for anyone outside your organization to see the app. It does not count toward the 12-tester, 14-day production access requirement, no matter how many internal testers you add or how long you run it.
Closed testing
This is the track the 12-tester requirement is actually about. Closed testing supports a defined group of testers — via email list, Google Group, or a shareable opt-in link — and requires each release to pass a review before testers can install it. For a personal developer account created after November 13, 2023, at least one closed testing track needs 12 testers opted in continuously for 14 days before the app can apply for production access. This is the track covered throughout the rest of this blog, including the full setup walkthrough.
Open testing
A public beta anyone can join via the Play Store listing itself, with no invite needed. Useful for gathering broader feedback before a full launch, and it can double as a way to build up real users pre-launch — but it isn't a substitute for closed testing on accounts subject to the requirement. Open testing participants aren't the same population Google evaluates for the 12-tester rule.
The mistake this causes
The most common version of this confusion: a developer runs internal testing with 12+ team members for weeks, assumes the requirement is satisfied, and only discovers otherwise when production access still isn't available. Internal testing simply isn't evaluated against this requirement at all — the fix is opening a closed testing track and starting the 14-day clock there, from scratch.
| Track | Who can join | Counts toward 12-tester rule? |
|---|---|---|
| Internal | Up to 100 named testers, instant | No |
| Closed | Defined list or opt-in link, after review | Yes |
| Open | Anyone via the Play Store listing | No |
If you've been running internal testing and just realized it doesn't count, the closed testing clock hasn't started yet — but the setup takes about 20 minutes, and we can take it from there for the full 14 days.
See how it works — from $24 →FAQ
Does internal testing count toward the 12-tester requirement?
No. Only closed testing counts toward the 12-tester, 14-day production access requirement.
Can I use open testing instead of closed testing?
No — open testing serves a different purpose (public beta feedback) and isn't evaluated against the closed testing requirement for new personal developer accounts.