If you are new to publishing on Google Play, the names of the testing tracks in Play Console sound almost the same. They are not, and picking the wrong one at the wrong time wastes weeks.
Here is what each track actually does, and which one matters for getting your app to production.
Internal testing
The fastest track. Up to 100 testers, builds available in minutes, distributed through a Play Store link or email list. Perfect for your own QA: you push a build, your team installs it, you find the crash on Android 12.
It does not count toward Google's 14-day closed testing requirement. None of it.
Closed testing
This is the track Google cares about for new personal developer accounts. You create a list of testers (email addresses), Google sends them an opt-in link, and they install the app from the Play Store.
The rule: at least 12 testers opted in continuously for 14 days before you can apply for production access. The clock is counted backwards from your application date — a tester who joined on day 10 has not been opted in for 14 days on day 14.
This is the only track that satisfies the requirement.
Open testing
Anyone with the link can join. Good for gathering feedback at scale once you are live, but for the 12-tester rule it changes nothing. Google does not count open testers toward the closed testing requirement.
Which track should you use, and when?
- Internal testing — during development, for your own devices and QA.
- Closed testing — the moment your build is stable enough for real users. This starts your 14-day clock, so do not delay it.
- Open testing — after production launch, for broader feedback.
The common mistake
Developers run two weeks of internal testing with their friends and then discover the 14-day clock never started. Only opted-in closed testers count. Start the closed test on day 1 of your "real" testing, not after.
Getting your 12 testers
Friends work until someone drops out halfway and your count falls below 12. If you cannot find 12 reliable people, services exist for exactly this: VerifiedTesters provides 12 real testers on their own Android phones for 14 continuous days, with a dashboard and free replacement if someone drops out.
Know your tracks, start the closed test early, and keep the count above 12. The rest is just patience.
Top comments (0)