Internal vs closed vs open testing on Google Play

Everything below comes from two Play Console Help articles: Set up an open, closed, or internal test and App testing requirements for new personal developer accounts. Numbers and rules are Google's; the advice on when to use each track is ours.

What are the testing tracks on Google Play?

Play Console offers three testing tracks before production: internal, closed and open. Each track holds its own releases. A device receives the highest version code published on the tracks its user is eligible for. Closed and open testers are also eligible for production, so if production carries a higher version code, they receive the production release instead.

Google recommends starting with an internal test, then expanding to a small group of closed testers. You can run internal tests alongside closed and open tests for different versions, and you can run several closed tests and one open test at the same time.

What is internal testing on Google Play?

Internal testing is for quick distribution to a small group of trusted testers. Google describes it like this:

• Up to 100 testers per app, added through email lists. A list can be reused for future tests on any of your apps.
• Fast. A new app bundle on the internal track reaches testers within minutes. A first upload is available to internal testers immediately, with a temporary name and store listing information for up to 48 hours.
• No prerequisites. You can start an internal test before completing your app setup.
• Anywhere. Internal testers get access even in countries where your app is not available, and device exclusion rules do not apply to them.
• Paid apps are free for internal testers, though in-app purchases are charged unless the tester is on a license testers list.
• Lighter checks. Google says internal tests might not be subject to standard Play policy or security reviews.
• Not searchable. Testers cannot find the app by searching Google Play; you share the Play Store URL or the opt-in link.

Internal testing does not satisfy the closed testing requirement for new personal accounts.

What is closed testing on Google Play?

Closed testing shares your app with a targeted group of users that you control, to fix issues and make sure the app complies with Google Play policy before launch. It is the track where new personal accounts run the required test.

• Three ways to add testers. Email lists (up to 200 lists, each with up to 2,000 users, and up to 50 lists per track), Google Groups (an address such as yourgroupname@googlegroups.com, whose members must join the group before opting in), or organizations that use managed Google Play.
• Needs a completed app setup. Google lists it as the requirement to access the track.
• Opt-in required. To be eligible, a user must be in the track's tester configuration and actively opt in. The opt-in link only shows once the app's status is Published, and testers see an explanation of their responsibilities before opting in.
• Slower first release. After the first publication of a test, Google says the test link can take several hours to become available, and later changes can take several hours too.
• More than one track. Play Console creates an initial closed track, and you can create additional ones, for example one per development team. Additional tracks do not support country targeting and a few other features.
• Paid apps are paid. Testers must purchase a paid app in closed and open tests.
• Private feedback. Testers can send private feedback through Google Play. They cannot leave public reviews on test versions, and their feedback does not affect your public rating.

Google Groups let you manage testers outside Play Console. TestBuddy works this way: you add its tester group to your closed test, and the developers in your wave opt in through your link. Our guide to setting up closed testing walks through the screens.

What is open testing on Google Play?

Open testing surfaces your test version on Google Play, so anyone can join and submit private feedback. Google asks you to make sure your app and store listing are ready to be seen publicly before you choose it.

• Visible. For a new app with no production release, users can find the open test through search on Google Play. For an app already in production, users can opt in from its store listing. Anyone with the link can join.
• Size. Unlimited by default, or a limited number of testers that must be at least 1,000.
• One at a time. You can run one open test per app.

For personal accounts created after 13 November 2023, the testing requirements article is explicit: "Open testing becomes available after you gain production access." It cannot be your route to production; it comes after.

Which testing track counts for the 12 testers requirement?

Closed testing. Google requires personal developer accounts created after 13 November 2023 to run a closed test with at least 12 testers who have been opted in continuously for at least 14 days before applying for production access. Internal testers do not count, and open testing is not available to these accounts until production access is granted.

Two details catch people out:

• Internal opt-ins block closed testing. Google states that a user who opts in to your internal test is no longer eligible for your open or closed tests, and receives only the internal version. If friends started on your internal track, ask them to opt out of it and opt in to the closed test; their 14 days start from that opt-in.
• One closed track is simplest. Google's help phrases the requirement around "a closed test" and does not say whether testers spread across several closed tracks add up. Keeping all your testers on one closed track avoids the question.

For the full rule and what Google asks when you apply, see the 12 testers for 14 days rule.

How do internal, closed and open testing compare?

Is internal app sharing the same as internal testing?

No. Internal app sharing is a separate tool: you upload an app bundle or APK on the internal app sharing page and share a download link, restricted to email lists or open to anyone with the link. Version codes do not need to be unique, debuggable builds are allowed, and uploads can be signed with any key. A link can be shared widely but at most 100 users can download through it, and links expire 60 days after upload.

Those uploads cannot be included in releases on testing or production tracks, so internal app sharing has nothing to do with the closed testing requirement. It is a convenient way to pass a build to a teammate.

When should you use each testing track?

Use internal testing for every build you want on a real device

It is the fastest route from upload to phone, it works before your store listing and app setup are finished, and it suits quality checks and debugging. Keep it to yourself and a few people who will not be in your closed test.

Use closed testing for the 12 testers and for pre-launch feedback

As soon as your app setup is complete, publish a closed test, add your tester list or Google Group, and share the opt-in link. Aim for more than 12 testers so a departure does not drop you below 12, and give them reasons to use the app every day: Google asks about engagement when you apply. Our guide to finding testers for closed testing compares the options. Additional closed tracks are useful later, when different teams test different features.

Use open testing once you have production access

For a new personal account, open testing comes after production access. It then works as a public beta: a wider audience, private feedback, and a test version anyone can find. Make sure your store listing is ready for public eyes first.

A typical path for a new personal account: an internal test for yourself, a closed test with 15 or more testers for at least 14 days, an application for production access, then open testing or a production release. If the application is refused, see what to do when production access is rejected.