Google Play internal vs closed vs open testing
Google Play has three testing tracks: internal testing for up to 100 testers with builds available within minutes, closed testing for invited testers by email list (up to 2,000 per list) or Google Group, and open testing that anyone can join from your store listing.
What are the three testing tracks?
Play Console has three testing tracks under Test and release, Testing, and each one is a separate release lane with its own testers. A build can move from internal to closed to open to production, or you can use only the tracks you need.
| Internal testing | Closed testing | Open testing | |
|---|---|---|---|
| Who joins | Up to 100 testers you list | Invited testers: email lists or Google Groups | Anyone, from your store listing or link |
| Size | 100 per app | 2,000 per email list; 200 lists per account, 50 per track; Groups unlimited | Unlimited by default, or a cap of at least 1,000 |
| Speed | Builds available within minutes | Normal review applies | Normal review applies |
| Counts for the 12-tester rule | No | Yes | No |
| Public reviews | No | No (private feedback only) | No (private feedback only) |
| Best for | Your team, daily builds | Beta groups, the 12-tester requirement | Large public beta before launch |
When should you use which?
- Every build, every day: internal testing. It is fast and limited to people you trust.
- A real-user beta: closed testing with a Google Group. Testers add themselves to the group, you do not manage addresses.
- New personal account before first launch: closed testing, with at least 12 testers opted in for 14 consecutive days. See the 12 testers for 14 days rule.
- A big public beta: open testing. People find it on your store listing and join with one tap. Set a cap if your servers or support cannot take an unlimited crowd.
How do testers join?
- You add testers to the track (email list, Google Group or, for open testing, nobody: it is public).
- You roll out a release to that track.
- You share the opt-in link from the track's Testers tab.
- The tester opens the link while signed in with the invited Google Account, accepts, and installs the app from Google Play.
Testers cannot leave public reviews on test versions. In closed and open tests they can send private feedback through Google Play, and Google asks you to provide your own feedback channel too, such as an email address or a forum.
Troubleshooting "item not found" and missing test apps
Work through this list in order:
- Wrong account. The tester's Google Play app is signed in with another Google Account. Have them switch account in Google Play, or add the address they actually use.
- Not opted in. Being on the list is not enough; the tester must open the opt-in link and accept.
- No release on the track. Adding testers does not publish anything; roll out a release to that exact track.
- Country not available. For closed and open tests, check the countries selected for the track.
- Fresh upload. On the first upload Google may show a temporary name and listing for up to 48 hours.
- Search. Test apps may not appear in Google Play search. Always share the link.
- Still in review. Closed and open releases go through the normal review before testers can install.
How do the tracks relate to TestFlight?
Apple's TestFlight works on a similar idea with different numbers: 100 internal testers, up to 10,000 external testers per app, a beta review for the first external build, and 90 days per build. Compare them in the TestFlight guide.
From testing to production
When testing is done, promote the build to production or create a new production release, as described in How to publish an app on Google Play. Review timing is covered in Google Play review time, and the panel layout in What is Google Play Console?.
Once the app is public, Uptika's Keyword radar reads your Google Play position for each keyword daily, per country, so you see from the first week which searches bring you up. The free plan tracks one app, one storefront and 10 keywords.
Questions
What is the difference between internal and closed testing on Google Play?
Internal testing is for up to 100 people you name, and builds reach them within minutes; it is meant for your team. Closed testing reaches invited testers through email lists or Google Groups, at much larger scale, and it is the track that counts for the 12 testers rule on new personal accounts.
Why does Google Play internal testing say item not found?
Most often the tester is signed in to Google Play with a different Google Account than the invited one, has not accepted the opt-in link yet, or the release has not been rolled out to the track. A first upload can also show a temporary listing for up to 48 hours.
How do testers download an internal testing app?
Send them the opt-in link from the track's Testers tab. They open it while signed in with the invited Google Account, accept the invitation, then install the app from the Google Play link on that page.
How many internal testers can I add?
Up to 100 testers per app on the internal testing track. For more, use closed testing (email lists of up to 2,000 people, or Google Groups with no size limit) or open testing.