Google Play closed testing: a developer's guide

Everything you need to know about Android closed beta testing on Google Play

Closed testing is Google Play's way of letting you distribute pre-release builds to a limited audience before going public. For personal developer accounts, it's also a mandatory gate before production access.

What is closed testing?

Closed testing (also called closed beta or closed track) lets you share your app with testers via an opt-in link. Testers must join through the link — your app won't appear in public Play Store search during this phase.

Closed testing vs open testing

• Closed testing: Invite-only via email lists or Google Groups. Required for personal accounts before production.
• Open testing: Anyone can join via a public link. Optional; useful for larger betas but not a substitute for closed testing requirements.
• Internal testing: Up to 100 testers, fast distribution, but doesn't count toward the 12/14 requirement.

The 12 testers / 14 days requirement

Personal developer accounts must demonstrate real testing before applying for production. Google requires at least 12 testers opted in for 14 consecutive days on a closed testing track.

Setting up closed testing in Play Console

Follow our detailed Play Store setup guide:

1. Create a closed testing track
2. Add tester emails or a Google Group (we recommend testflock@googlegroups.com)
3. Enable all countries and regions
4. Upload your APK/AAB and submit for review
5. Copy the opt-in link and share it with testers

How TestFlock fits in

TestFlock doesn't replace Play Console — it helps you match with fellow developers who will actually complete the closed testing period. Flocks provide structured reciprocal testing with daily accountability.