Internal vs closed vs open testing on Google Play

Google Play has three test tracks before production. Internal testing gets builds to up to 100 people fast. Closed testing shares your app with a group you control, and it is the only track that counts for the 12-tester rule. Open testing lets anyone join, but new personal accounts only unlock it after production access.

That's the short version. The details matter, because one of them quietly breaks a lot of closed tests.

The three tracks side by side

Sources: Set up an open, closed, or internal test and App testing requirements for new personal developer accounts.

Internal testing: fast, small, outside the rule

Internal testing is for you and a few trusted people. Google lists what makes it different (Play Console Help):

• Up to 100 testers per app, managed with email lists.
• You can start before your app setup is complete. Only a valid app bundle is needed.
• New builds reach testers within minutes. On a first upload, testers see a temporary app name and store listing for up to 48 hours.
• Device exclusion rules don't apply to internal testers.
• Paid apps are free for internal testers. In-app purchases are not, unless you add testers as license testers.

One catch: internal doesn't mean "no review". If your app's first release goes to the internal track, it goes through Google's review before it's published, and that can take "a few hours or up to seven days (or longer in exceptional cases)". The same applies to the next submission after a rejection (Play Console Help).

Use internal testing to catch crashes on your own devices before strangers see the app. Don't count on it for the requirement.

Closed testing: the track the rule is about

Google's wording is direct: new personal accounts "must run a closed test for their app with a minimum of 12 testers who have been opted in continuously for at least 14 days" before applying for production (Play Console Help).

What you should know about the closed track (Play Console Help):

• It needs a complete app setup. That's the only access requirement Google lists for the closed track (Play Console Help).
• A default closed track exists. You can add more with Create track and give each one a name.
• Testers come from email lists or Google Groups. Email lists have limits: 200 lists per developer account, 50 per track, 2,000 testers per list. Google Groups have no size limit. A Workspace group must be on your developer account's domain; otherwise use a @googlegroups.com group.
• The opt-in link only appears when the app status is "Published". After the first publish, it can take several hours before the link works for testers.
• Paid apps cost money in closed tests. Google says testers must purchase paid apps in open or closed tests.
• Extra closed tracks have limits. They don't support country targeting or enterprise targeting, among others.

The step-by-step setup is in How to set up a closed test.

Open testing: locked until production access

Open testing puts a test version on Google Play where anyone can find and join it. Testers send private feedback. You can leave it unlimited or set a cap of at least 1,000 testers.

For personal accounts created after November 13, 2023, Google's track table is clear: open testing requires that you "gain access to production" first (Play Console Help). So it's not a shortcut around the closed test. It's a tool for later, when you want a public beta of an app that already passed.

The trap: internal testers can't get your closed test

This one costs developers days. Google states it plainly (Play Console Help):

"A user who opts into your app's internal test is no longer eligible to receive an open or closed test. To access an open or closed test, the user must first opt out of the internal test and then opt in to the open or closed test."

And in the version code section: "Users who opt into internal testing aren't eligible for open and closed testing, even if included as testers on those tracks. These users receive only the version code published on the Internal testing track."

How it usually happens:

1. You add yourself, a cofounder and three friends to an internal test. Everyone opts in.
2. Your app setup is done, so you start the closed test and add the same people.
3. They open the closed opt-in link, but they're still internal testers. They keep receiving the internal build, not your closed test.

Google doesn't say how these people show up in your closed tester count. Don't find out the hard way. Before the 14 days start, ask anyone who joined your internal test to leave it.

On the tester's phone, leaving is in the Play Store: profile icon, Manage apps & devices, Beta, open the app, then Leave under "You're a beta tester" (Google Play Help). Then they open your closed test opt-in link and join again.

If your count looks lower than the number of people who joined, this is one of the first things to check. More causes are in Testers not counted.

Version codes across tracks

Each device gets the highest version code it's eligible for. Users in your closed test are eligible for the closed track and production. Users in the internal test only get the internal track (Play Console Help).

Two practical rules follow:

• Bump the version code for every build you publish to the closed track. A lower number than another track they're eligible for won't reach them.
• Watch the release warnings. Play Console tells you when a track is "Shadowed", "Superseded" or "Partially shadowed" by another one. "Superseded" means none of that track's bundles reach anyone.

Can you run tracks at the same time?

Yes. You can run multiple closed tests and one open test at the same time, and internal tests in parallel for different versions (Play Console Help). Just keep each person on one track.

Which track to use, in order

1. Internal testing for your own devices and teammates. Fix crashes, broken sign-up, missing screens.
2. Closed testing for the requirement: at least 12 testers, opted in for 14 days in a row, plus real feedback you can summarize in the production access form. Recruit more than 12 so one person leaving doesn't reset your date. How to get 12 testers compares the options.
3. Apply for production from the Dashboard once you qualify.
4. Open testing later, if you want a public beta.

For the full picture of the requirement, start with the Google Play closed testing guide.