Play Console gives you three testing tracks — internal, closed and open — and on a new personal developer account, only one of them leads to production. Here's how internal and closed testing differ, which one satisfies Google's requirement, and why using both with the same testers can backfire.
The short answer
- For new personal accounts, the closed test is the required one: at least 12 testers, opted in continuously for at least 14 days.
- Internal testing is optional — Google recommends it as a starting point.
- Open testing only becomes available after you gain production access.
On this page
Side-by-side comparison
| Internal testing | Closed testing | |
|---|---|---|
| Purpose | Quick checks with a small, trusted group | Pre-production testing with a controlled group |
| Tester limit | Up to 100 testers per app | Email lists of up to 2,000 users each (up to 50 lists per track), or Google Groups |
| Speed | New builds reach testers within minutes | Changes are reviewed before publishing; a first-time opt-in link can take several hours |
| Policy review | Might not be subject to standard Play policy or security reviews | Changes are sent for review |
| Paid apps | Testers install for free | Testers must purchase |
| Counts toward 12 testers / 14 days | No | Yes — this is the required test |
| Required for production access (new personal accounts) | No — optional | Yes |
When to use internal testing
Internal testing is a fast feedback loop for you and a handful of people you trust. A build you upload reaches internal testers within minutes, which makes it useful for smoke-testing a release before your closed testers see it. It's optional, and it doesn't count toward the requirement, however many testers you add.
When to use closed testing
For a new personal account, closed testing isn't a choice — it's the test Google evaluates. Your 12+ testers need to be opted in to the closed track, continuously, for at least 14 days before you can apply for production access. Our closed testing setup guide walks through it step by step, with a video.
The overlap rule that removes testers
This is the one that catches people out. Google's documentation states that a user who opts in to your app's internal test is no longer eligible to receive an open or closed test. To join the closed test, they have to opt out of the internal test first, then opt in to the closed test.
So if you put your closed testers on the internal track too — to give them early builds — some of them may never actually be in your closed test, and won't count. It's one of the causes covered in why testers aren't counting.
Keep the two groups separate
Use internal testing for yourself and a few trusted people; put the testers you need for the requirement on the closed track only. If anyone is on both, ask them to opt out of the internal test and re-open the closed-test link.
Where open testing fits
Open testing lets anyone join and makes your test visible on Google Play. For new personal accounts, though, it only becomes available after you've gained production access — so it can't substitute for the closed test.
A sensible order
- 1
Internal testing (optional)
Upload a build and check it installs and the core flow works on a couple of devices.
- 2
Closed testing (required)
Roll out to your closed track, get 12+ testers opted in, and run the full 14 days with real use and feedback.
- 3
Apply for production access
From the Dashboard, once the requirement is met. Google asks about your closed test, your app, and your production readiness — see production access questions & answers.
- 4
Production — and open testing if you want it
Both become available once production access is granted.
Frequently asked questions
Does internal testing count toward the 12 testers requirement?
No. For new personal developer accounts, the requirement is a closed test with at least 12 testers opted in continuously for at least 14 days. Internal testing is optional and doesn't satisfy it, however many testers you add.
Can I skip internal testing?
Yes. Google describes internal testing as optional but recommended as a starting point. Many developers go straight to the closed track; internal testing is mainly useful for quickly checking a build before your closed testers see it.
Can the same person be an internal and a closed tester?
Not at the same time. Google says a user who opts in to your internal test isn't eligible for your open or closed test; they must opt out of the internal test and then opt in to the closed test.
Can I use open testing instead of closed testing?
Not on a new personal account. Open testing only becomes available after you gain production access, so the closed test has to come first.
Is internal testing reviewed by Google?
Google notes that internal tests might not be subject to standard Play policy or security reviews, which is part of why builds reach internal testers within minutes. Don't treat that as a loophole — it doesn't count toward production access.
How many testers can internal testing have?
Up to 100 testers per app. Closed testing scales much further, with email lists of up to 2,000 users each, or Google Groups.
Official sources