Google Play Internal Testing vs Closed Testing
A simple comparison of internal and closed testing, and which one you need before applying for production.
Read the guide →Google Play Closed Testing vs Open Testing
Quick answer In closed testing vs open testing, a closed test admits only people you invite, while an open test is public. New personal accounts need the closed test to unlock production access.
Google Play has three testing tracks, and developers often confuse closed testing with open testing. They sound similar, but they work very differently, and only one is the track new personal accounts must use before applying for production. Here is a clear comparison.
The short answer
A closed test is private. Only the people you invite can join, using an opt-in link. An open test is public. Anyone with the link, or anyone who finds the app on Google Play, can join. If you have a new personal developer account, the closed test is the one that matters for production access.
Closed vs open testing at a glance
These details come from Google's Play Console Help page on testing tracks.
- Who can join a closed test: testers on your email lists or Google Groups, or members of an organization.
- Who can join an open test: anyone with the link, or anyone who finds the app on Google Play.
- Tester limits: a closed test allows up to 200 email lists of up to 2,000 users each, and up to 50 lists per track. An open test is unlimited by default, or you can set a limit of at least 1,000.
- Visibility: a closed test is not searchable on Google Play. An open test is public, and early-access apps are searchable.
- Reviews: test versions in both tracks cannot receive public reviews.
- Paid apps: testers must purchase the app in both tracks.
When should you use closed testing?
- You need to meet the 12-tester, 14-day requirement for production access.
- You want feedback from a chosen group before the public sees your app.
- You want to keep the app hidden from search while you fix bugs.
Setting up a closed test takes a few minutes. Our guide on adding testers to Google Play Console walks through every step.
When should you use open testing?
- You want a large number of real users to try the app before launch.
- You want early-access visibility on Google Play.
- You have already finished your required closed test and want broader feedback.
Careful: an open test is public, so make sure your store listing, privacy policy and data safety information are ready before you start one.
Which one counts for production access?
For personal accounts created after November 13, 2023, Google asks for a closed test with at least 12 testers opted in continuously for 14 days. Read the official requirement, or our plain-language guide to the 14-day closed testing requirement. If you are also deciding about internal testing, see internal testing vs closed testing.
How to decide in 30 seconds
- Is this a new personal account? Run a closed test first. It is the requirement for production access.
- Do you want the world to see the app before launch? Consider an open test after your closed test is complete.
- Is your listing and privacy policy ready? If not, stay with closed testing, because open tests are public.
- Do you need a very large group? An open test has no tester limit by default, while a closed test is limited by email lists.
Common mistakes
- Running an open test and expecting it to satisfy the closed test requirement.
- Sharing a closed test link publicly. Anyone with the link can try to join, so share it only with the people you chose.
- Forgetting that testers of paid apps must purchase the app.
Not sure how to add people to your closed test? Follow our step-by-step guide, and read why testers sometimes do not count if your numbers look wrong.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
A recommended setup for a new app
- Internal test firstUpload your bundle, check it installs and runs. See internal vs closed testing.
- Closed test secondAdd 15 to 20 testers and run 14 days. See how to get 12 testers.
- Apply for productionFollow how to apply for production access.
- Open test is optionalUse it later if you want public beta feedback before launch.
Privacy and control
A closed test keeps feedback private and limits who can install your app. An open test exposes your listing to anyone, which can mean strangers' feedback and early reviews of an unfinished product. Google notes testers cannot leave public reviews on test versions, but open testers can still see your app listing.
Limits compared
| Question | Closed | Open |
|---|---|---|
| Who can join | People on your lists, groups or organizations | Anyone with the link or from Google Play |
| Searchable on Google Play | No | Yes |
| Counts for new personal accounts | Yes | Check Google's current requirement page |
| Best for | Controlled feedback | Public beta |
Frequently asked questions
Which testing track do new personal accounts need?
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers opted in for 14 days before they can apply for production access.
Can I run closed and open tests at the same time?
Yes. Google says you can run multiple closed tests and one open test at the same time.
Is a closed test visible on Google Play search?
No. A closed test is not searchable on Google Play. Testers join with an opt-in link that you share.
How many testers can a closed test have?
Google allows up to 200 email lists of up to 2,000 users each, and up to 50 lists per track.
