Play Console gives you three ways to test an app before it goes public: internal testing, closed testing and open testing. They differ in who can join, how fast updates arrive and what they unlock. The figures below are from Google's help page on test tracks.
Internal testing
- Up to 100 testers, added by email list.
- New builds reach testers within minutes.
- No requirements: you can start right away.
- Internal tests might not go through the standard policy and security reviews.
Use it for your own team and a few trusted people while you build. It does not meet the requirement for new personal accounts.
Closed testing
- Testers are added with email lists or Google Groups. Group members join the group first, then opt in through the test's opt-in link.
- The first time you publish a closed test, it can take several hours before the link works; later updates also take several hours.
- Requires a completed app setup in Play Console.
This is the track that matters for new personal developer accounts: 12 testers opted in for 14 days in a row unlock production. Google Groups are the practical way to add many testers: you add one group address to the test, and whoever manages the group adds or replaces testers without touching your Play Console.
Open testing
- Anyone can join, through a link or by finding the test on Google Play.
- Needs production access first, so it comes after the closed test for new accounts.
Which to use when
- While building: internal testing with your team.
- Before launch: a closed test with at least 12 real testers for 14 days, to unlock production and get feedback. Make sure they actually use the app.
- Apply for production: answer Google's questions about the closed test, then go live or start an open beta.
Testers in a test can't leave public reviews for test versions, and their feedback doesn't affect your public rating, so a closed test is a safe place to find problems.
Need the testers? Beta Family gives you a Google Group to add to your closed test, and fills it with 15 testers for the 14 days. See the Google Play Production Pass.
More guides to Google Play testing
- Google Play's 12 testers for 14 days rule, explainedNew Google Play developer accounts need 12 testers in a closed test for 14 days before they can publish. What counts, and how to get through it fast.
- How to answer Google Play's production access questionsAfter 14 days of closed testing, Google Play asks three sets of questions before production access. What it asks, and how to answer each part well.
- Why Google Play asks for more testing, and how to avoid itGoogle Play can ask for more testing when testers weren't engaged enough or fewer than 12 stayed opted in. How to keep your testers active for all 14 days.
