In this guide
An open test puts your pre-release app in front of a large group and makes it visible on Google Play. Facts below are from Play Console Help, retrieved 2026-10-24.
How an open test works
- You run "a test with a large group and make your test version visible on Google Play."
- Tester cap: unlimited (the default) or a limited number, which must be at least 1,000.
- Anyone with the shareable link can access the test.
- Make sure the app is ready for public visibility first.
- Testers cannot leave public Play reviews for test versions. They can give private feedback through Google Play in open and closed tests.
Open vs closed
| Closed test | Open test | |
|---|---|---|
| Who joins | People you invite (email lists) | Anyone with the link; also visible on Google Play |
| Size | Up to 200 email lists of up to 2,000 users each; up to 50 lists per track | Unlimited or at least 1,000 |
| Control | High | Low |
| Good for | Targeted feedback, the new-account requirement | Wide device coverage, public beta |
| Risk | Few testers, little variety | Unpolished app visible to anyone |
The new-account requirement
For new personal accounts, the requirement is stated as a closed test with a minimum of 12 testers opted in continuously for at least 14 days. Source: Play Console Help, retrieved 2026-10-24. The same page says open testing "becomes available after you gain production access", so it cannot stand in for the closed test. Plan the closed test.
When open testing makes sense
- Your app is stable and you want wider device coverage than your testers have.
- You already have a production version and want to try a big change with willing users.
- You want a public beta and accept that anyone can join.
When to skip it
- The app is still rough. Fix it in internal and closed tests first.
- You need to control who tests.
- You must meet the closed-test requirement. That is a separate step.
Example: a note-taking app that already has production access runs an open test for a month before a big update to see more phones.
Related
Back to the Google Play closed testing guide. See also promote a closed test to production and the closed test calendar. Track overview: internal, closed, open testing.
AppReviewX test groups for Google Play: 12 testers, 14 days in a row, Android apps, with private, structured feedback. Start here.
Policies change; check the linked help pages before you decide.