Canonical guide
Google Play closed testing, without roster guesswork
You need 12 testers opted in continuously for 14 days. Treat roster stability, access, and real feedback as separate things you must verify.
Checked and updated August 2026
The requirement in plain English
- Create and publish a release to a closed testing track.
- Give eligible testers access through a Google Group or email list.
- Keep at least 12 people opted in for 14 continuous days.
- Use their real feedback when answering the production access questionnaire.
What the daily check-in means
It is a TesterSwap reliability signal for closed beta commitments. It is not a claim that Google mandates a daily app open. Live-app reviews never use this 14-day check-in flow.
Common failure points
- Tester joined the group but never opened the opt-in URL.
- The release is unavailable in the tester's country.
- The roster drops below 12 during the continuous window.
- The production questionnaire describes intentions instead of observed testing.
Questions developers ask
How many Google Play closed-test testers are required?
For newly created personal developer accounts, Google Play currently requires at least 12 opted-in testers for 14 continuous days before production access can be requested.
Do testers need to open the app every day?
Google publishes an opt-in duration requirement, not a public daily-open rule. TesterSwap daily check-ins are evidence that a closed-beta commitment is still active.
Can I exchange reviews during closed testing?
No. Store reviews belong to already-live apps and use a separate, policy-aware Review Swap after a tester has real product experience.