Closed testing vs open testing: which Google Play track counts?
Google Play has four tracks: internal, closed, open and production. Only closed testing (with the required tester count and duration) satisfies the requirement for new developer accounts.
The four tracks
- Internal testing — up to 100 testers you invite, available immediately, does not count toward the requirement
- Closed testing — invite-only testers, 12+ testers for 14 consecutive days, this is the track Google checks
- Open testing — public beta anyone can join, useful later but not a substitute for closed testing
- Production — your public release, unlocked after the closed testing requirement is met
Who can join each track
Internal and closed testing are invitation-based: testers must join through your Google Group or testing link and opt in with their own Google account. Open testing uses a public link anyone can use.
What we recommend
Use internal testing for your own smoke tests, then move to closed testing with at least 12 testers for 14 days. Add a buffer so a single opt-out does not reset the clock, and collect written feedback during the cycle — it makes your production access application much stronger.
FAQ
See all FAQDoes open testing count toward production access?
No. The requirement is tied to closed testing. Open testing is useful for feedback, but it does not replace the closed testing period.
Can internal testers count as my 12 testers?
No. Internal testing does not count toward the requirement — testers need to join through your closed testing track.
How many testers can join a closed test?
Google allows a limited number of testers per closed test; you only need to hit the minimum required for your account, with a small buffer.
Managed closed testing · $10 all-inclusive
15 real testers, 14 days active + 2 buffer days, test report before day 10.