DEV Community

Dev Connect
Dev Connect

Posted on • Originally published at devconnectplatform.com

Google Play testing tracks explained: internal, closed, open, and which one gates production

Google Play gives you three testing tracks plus production, and the names do not make the differences obvious. Here is what each one is for and which one is standing between you and shipping.

Internal testing

Up to 100 testers, available within minutes of upload, no review to wait for. This is your build-and-check loop, meant for your own team and people you can message directly.

What it is not: internal testing does not count towards the closed-testing requirement. People lose days here assuming it does.

Closed testing

A limited group you invite by email list or Google Group. Reviewed by Google before testers can install, so expect a wait on the first release.

This is the track that gates production. If your personal developer account was created after 13 November 2023, you need at least 12 testers opted in to a closed test for 14 continuous days before you can apply for production access. The days only count while the number stays at 12 or above, which is the detail that costs people weeks.

Open testing

Anyone with the link can join, and your app appears in Play with a "Early access" label. Good for gathering real-world feedback at volume, useful for stability data on many device models.

Open testing does not replace the closed-test requirement either. It is a distribution choice, not a shortcut.

Production

What you are trying to reach. After you have met the closed-testing requirement you apply for production access, and Google reviews the app. That review usually takes a few days, sometimes longer, and it is a separate wait from the 14 days.

The order most people end up using

Internal while you are still fixing things, because it is instant. Closed as soon as the build is worth two weeks of someone's attention, because that clock is the long pole. Open afterwards if you want broader feedback before production.

The practical consequence is that you should start recruiting closed testers earlier than feels necessary. The build does not have to be finished, it has to be installable and not embarrassing, because the two weeks run in parallel with the work you are still doing.

If you are in that closed test now, count the days from when you actually had 12 opted-in testers rather than from upload: https://devconnectplatform.com/tools/closed-test-tracker

Top comments (0)