Internal, closed and open testing: the differences
In short: internal testing is small and fast, with up to 100 people. A closed test runs with people you choose, and it's the test the 12-tester requirement calls for. Anyone can join an open test; on new personal accounts it only becomes available after you gain production access.
12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.
See packsThe three tests side by side
| Internal testing | Closed testing | Open testing | |
|---|---|---|---|
| Who can join | People you add to an email list | People on an email list or in a Google Group | Anyone who wants to |
| How many | Up to 100 per app | Up to 2,000 per list; no limit for a Google Group | Unlimited, or a limit of at least 1,000 |
| When it's available | Even before app setup is complete | Once app setup is complete | On new personal accounts, after you gain production access |
| Review | May not go through standard review; reviewed if it holds the app's first release (except apps that aren't fully configured) | Reviewed | Reviewed |
| 12-tester requirement | Doesn't meet it; the requirement calls for a closed test | This is the test the requirement calls for | Available once the requirement is met |
| Paid apps | Testers install for free | Testers buy the app | Testers buy the app |
The table is based on Google's pages on setting up tests, testing requirements and review. On a phone, you can scroll the table sideways.
Internal testing
Google describes internal testing as quick distribution to “a small group of trusted testers”: “Builds are normally available to testers within seconds of being added in Play Console.” It's optional, but Google recommends it as a starting point.
There's an important catch. In Google's words: “Users who opt into internal testing aren't eligible for open and closed testing, even if included as testers on those tracks.” If you want the same person in your internal test first and your closed test later, they need to leave the internal test first.
Closed testing
A closed test shares your app with “a targeted group of users that you control”. For personal accounts created after November 13, 2023, the road to production runs through it: “You must run a closed test before applying to publish your app to production.” Internal testing doesn't meet this requirement. The numbers, too, are set for the closed test: “At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.”
You can run several closed tests at the same time. We walk through the setup step by step in the guide to setting up a closed test.
Open testing
An open test shows your app's test version to everyone on Google Play; anyone can join and send private feedback. Google's warning: before choosing this option, make sure your app and store listing are ready to be seen publicly. On new personal accounts: “Open testing becomes available after you gain production access.” You can only run one open test at a time.
Which one should you use, and when?
- Before setup is complete: internal testing. Catch the first bugs on your own devices and with a few people you trust.
- Once setup is complete: closed testing. Get at least 12 people to opt in and keep them opted in for 14 days in a row. Collect the feedback that comes in during that time and act on it; the application form asks about it.
- When the 14 days are up: apply for production access. The questions are in the application form guide.
- After approval: production and, if you like, open testing.
Sources
- Set up an open, closed, or internal test
- App testing requirements for new personal developer accounts
- Control when app changes are reviewed and published
- Publish your app
All are Play Console Help pages.
12 testers plus 3 backups, 14 days in a row. Follow every day on a live table.
See packs