What closed testing is: internal vs closed vs open

Closed testing is one of the three release tracks Google Play offers before an app goes fully public — internal, closed, and open. It's the one built around real people opting in: you name specific testers by email address or Google Group, then copy the opt-in link from Play Console and share it with them yourself. Google does not send the invitation for you — each tester must open that link and join before their install counts toward the requirement.

For a personal developer account created after November 13, 2023, closed testing isn't optional — it's the gate. Google Play won't show the production-access application until a closed test has run with at least 12 opted-in testers, opted in continuously, for 14 straight days. "Continuous" matters: it's not 14 cumulative days, it's 14 days where the count never dips below 12.

How the three tracks differ

Internal testing is capped at 100 testers, added by email, with no minimum duration — it's built for a developer's own quick sanity checks, not for satisfying any Google requirement.

Closed testing is the one that counts: 12+ testers, invited by email or Google Group, opted in continuously for 14 days. It's also the only track where Google tracks a specific opted-in count against a specific continuous-day requirement — internal and open testing don't have an equivalent bar to clear.

Open testing is the most public option: anyone can join by finding the app on Google Play or via a shared link, with no invite list at all, and no upper limit on participants. It's meant for a broader public beta once an app is already further along — it doesn't substitute for the closed-testing requirement either, since Google doesn't track a continuous opt-in streak on it the way it does for closed testing.

Why the requirement exists

The point of the requirement, from Google's side, is that an app has actually been run by real people on real devices before it reaches the full Play Store — not just uploaded and published. That's also why the production-access questionnaire afterward asks what those testers actually did, not just how many opted in.

In practice: internal testing is for you and your team, closed testing is the 12-tester/14-day requirement itself, and open testing is an optional public beta for later. Testers14 supplies real testers specifically for the closed-testing track, since that's the one Google actually checks — so the only thing left for you to do is watch the dashboard and answer Google's questionnaire once the days are done.