Closed testing vs beta testing on Google Play

"Beta testing" is the everyday phrase. "Closed testing" is the Google Play track name.

They overlap, but they are not identical. If you are trying to satisfy Google's 12-tester, 14-day requirement, the distinction matters.

The short definition

• Closed testing is a Google Play testing track that limits access to a list of testers you choose.
• Beta testing is a general product-development term for giving an unfinished app to a limited group before a wider release.
• Open testing is a Google Play track that anyone can join, subject to your settings.
• Internal testing is a small, fast track for your own team.

A closed test can be a beta test. A beta test does not have to be a Google Play closed test.

The Google Play tracks

Google Play gives you several ways to release a build:

For covered personal developer accounts created after 13 November 2023, Google's production-access requirement is tied to closed testing with at least 12 testers for 14 continuous days. Internal testing and open testing are not a substitute for that specific requirement.

Why people say "beta"

Most developers come from a world where "beta" means "a build before launch." Google Play's UI uses "testing tracks," and the closed track is the closest thing to a classic private beta.

If a guide says "you need a 14-day beta test," check whether it means Google Play's closed testing requirement. The rule is about the closed track, not about the word beta.

What counts for production access

A qualifying closed test generally needs:

• at least 12 testers;
• real Google accounts, not accounts you control;
• 14 continuous days opted in;
• the closed track active;
• a production-access application after the test.

A polished beta with 30 testers on the open track is useful, but it does not automatically satisfy the 12-tester closed-testing rule.

When to use each track

• Use internal testing for a quick sanity check with your team.
• Use closed testing for the 12-tester requirement and controlled feedback.
• Use open testing when you want a public beta and do not need a fixed tester list.
• Use production only when you are ready for real users or have been approved.

You can use more than one track over the life of an app. The tracks are not mutually exclusive.

Common mistake: starting in the wrong track

A developer invites 12 people to internal testing, waits 14 days, and expects production access. The Console does not show the closed-testing requirement as satisfied because the test was not on the closed track.

Check the track name before you invite anyone. The requirement is specific.

The short version

• Closed testing is a Google Play track; beta testing is a general term.
• The 12-tester, 14-day rule applies to closed testing for covered accounts.
• Internal and open testing are different tracks.
• A beta test only counts for production access if it is the right closed test.
• Read the Console requirement, not the label on a guide.

Next: internal vs closed vs open testing or which accounts need closed testing?.