Guides & FAQs

All guides

Background·4 min read

Internal vs closed vs open testing

What each Google Play track is for, and the only one that counts toward production.

Play Console offers three testing tracks before production. They look similar in the interface, but they serve different jobs, and only one of them satisfies Google's 12-testers requirement. Only closed testing is mandatory: internal and open testing are optional extras you can skip entirely, and a closed test alone takes your app live on the Play Store.

InternalClosedYoursOpen
PurposeTeam QA, crash huntingStructured beta with invited usersPublic beta, anyone can join
Max testers100Very large (email lists or Google groups)Unlimited
Who can joinOnly listed emailsInvited via email list or Google groupAnyone with the link
Review before liveNone, near instantYes, first release is reviewedYes
Visible on Play StoreNoNo, opt-in link onlyYes, as early access
Counts toward the 12 testers requirementNoYesNo
Available to new personal accountsYesYesOnly after production access
  1. 1

    Internal testing: optional

    You plus a few teammates, up to 100 people. Releases go live in minutes with no review, which makes it handy for catching obvious crashes early, but it is entirely optional: you can start directly with closed testing.
  2. 2

    Closed testing: the only mandatory track

    The one required stage, and the one we run for you: 12+ real testers opted in for 14 days, plus two free buffer days on top. This is the only track that unlocks production access, and completing it is all your app needs to go live.
  3. 3

    Apply for production access

    Answer the 10-question form with the concrete feedback your closed test produced.
  4. 4

    Open testing: optional, later

    A public beta listed as early access on the Play Store. It only becomes available after production access, useful for a soft launch at scale once your app is already solid. Like internal testing, skip it freely unless you want it.

Two traps worth knowing

Internal testing contributes nothing to the 12-testers requirement, no matter how many people you add or how long they test. And a tester counts where they opted in: someone who joined your internal track does not count as a closed tester, even if they use the app daily.