Closed Test vs Open Test: Which Google Play Track Do You Need?

Closed testing and open testing are both called beta tracks, and the names suggest a simple difference in size. In practice they do different jobs, only one of them counts toward your production access requirement, and picking the wrong one can cost you weeks. This comparison explains what each track is for and the order most developers should follow.

Closed test vs open test at a glance

Which track counts toward the requirement

This is the single most important row in the table above. If your goal is production access, your requirement-counting test has to run on the closed testing track, using testers you invited and who opted in through your shareable link.

What each track is genuinely good at

Closed testing: control

Closed testing lets you choose exactly who installs your app. You can recruit people who match your audience, give them specific tasks, and get detailed reports back. That control is why Google made it the requirement track: the people testing are a deliberate, real group rather than whoever wandered in.

Open testing: reach

Open testing trades control for reach. Once you have production access, an open track is a useful way to collect early impressions from a wide, unpredictable audience before you hand the app to everyone in production.

A sensible order of operations

1. Use internal testing first to shake out the build with your own team (up to 100 users).
2. Move to closed testing and run the 12-tester, 14-day window that satisfies the requirement.
3. Apply for production access and wait for the decision.
4. After launch, consider an open test for broad feedback, or go straight to staged production rollouts.

Each track reviews releases separately, so the sequence above also keeps your review queue predictable. If you would rather have someone else sequence the whole pipeline, AppsTestLab runs closed tests and full track setups for teams shipping on a deadline.