Google Play Closed Testing vs Open Testing: What's the Difference?

Google Play offers four testing tracks: internal, closed, open, and production. Most developers only need to understand two of them: closed and open. They work differently, have different requirements, and serve different purposes.

Quick summary

Closed testing: what it is and when to use it

Closed testing is a controlled testing track where you invite specific people to test your app. Testers must be added to a Google Group or Google Workspace domain that you manage. They can only join using the email address associated with that group.

Closed testing is the track that counts toward production access for personal developer accounts. You need 12 active testers for 14 consecutive days in the closed track before Google will allow you to apply for production.

Use closed testing when:

• You need to complete the production access requirement
• You want to control exactly who tests your app
• Your app is not ready for public visibility
• You're testing with a small, known group of people

You can have multiple closed testing tracks — for example, one for internal QA and another for external beta testers. Each track has its own tester list and opt-in link.

Open testing: what it is and when to use it

Open testing (also called open beta) lets anyone join your test. Your app gets an "Early access" badge on the Play Store and can appear in search results. Any Google account can opt in without an invitation.

Open testing does not count toward your production access requirement. The 14-day counter only runs on the closed track.

Use open testing when:

• You already have production access and want public beta feedback
• You want to gather a large number of real users before full launch
• You're comfortable with your app being publicly visible
• You want to run an open early access program

Reviews left during open testing are publicly visible on the Play Store. This is different from closed testing, where feedback is private. Be careful launching open testing on an app that isn't ready — public bad reviews can affect your launch.

Can you run both at the same time?

Yes. You can have closed testing and open testing running simultaneously on different tracks. Testers in closed testing see the closed track build; open testers see the open track build. These can be different APK versions if needed.

In practice, most indie developers don't need to run both at once. The typical path is:

1. Internal testing (unlimited, no opt-in, just for your own testing)
2. Closed testing (12 testers, 14 days — to meet production access requirement)
3. Production (or optionally open testing before full production)

Internal testing vs. closed testing

There's also a fourth track worth mentioning: internal testing. Internal testing has no tester count requirements and no 14-day wait. You can add up to 100 testers via email address (no Google Group needed), and releases go live almost immediately (minutes instead of hours).

Internal testing is useful for testing your own app on different devices, or for sharing a build with a small team before wider closed testing. It does not count toward production access.

A common mistake: using open testing to meet the production requirement

Some developers, confused by the track names, run open testing and expect it to count toward production access. It doesn't. The production access requirement is specifically for the closed testing track. Open testing testers do not count, regardless of how many you have or how long they've been active.

If you've been running open testing and waiting for the production access button to appear — switch to closed testing. Set up a Google Group, get 12 testers to opt in, and start the 14-day counter there.

Which track should you start with?

If your goal is to publish on Google Play as quickly as possible:

1. Start with internal testing to verify your build works
2. Move to closed testing with 12 real testers to start the 14-day counter
3. After production access is granted, decide whether to launch directly or run an open beta first

Don't overthink the track structure. Most indie developers never need open testing at all — they go directly from closed testing to production.

Frequently asked questions

Related articles