Internal, closed and open testing on Google Play
Google Play has three test tracks and they are easy to mix up. They differ in who can join, how fast changes arrive and what Google expects from you.
Internal testing
Up to 100 testers you list by email. New builds reach them within minutes, no review wait. Use it for your own team and quick checks of a build before it goes anywhere else. It is not meant to show real-world behavior at scale.
Closed testing
You choose the testers through email lists or a Google Group, and only they can opt in. This is the track tied to the production requirement for new personal developer accounts. Use it to collect feedback from people outside your team and to run the required test period. See our guide to the 12 testers rule.
Open testing
Anyone can find your app on the Play Store and join. Open tests suit a late beta when you want real device variety and public listing exposure. Because strangers can join, expect more reviews and more noise.
Which one when
- Every build: internal, to catch obvious breakage in minutes.
- Before production: closed, with concrete tasks for testers.
- Shortly before launch: optionally open, if you want volume and can handle feedback from the public.
Questions developers ask
Can I move a build from one track to another? Yes, you can promote a release between tracks in the Play Console instead of uploading again.
Does internal testing satisfy the production requirement? The requirement refers to a closed test. Confirm the current rules in Google Play Console Help.
Need testers for your app? Open a test group on AppReviewX. Start free