Play Console · closed testing
Google Play Closed Testing: Requirements (12 Testers, 14 Days)
What Google Play closed testing is, how it differs from internal and open testing, how to set it up and invite testers, and what Google requires (12 testers, 14 days) before production access.
When the release checklist pushes you toward closed testing, the bottleneck is usually the tester quota: real people who join the track and install the build. Tester Marketplace helps you organize that quota with campaigns and usage evidence — without replacing official Play Console setup.
What you need in practice
- A list or join flow for the closed track.
- Installable builds matching the app package.
- Often sustained use (sessions), not just “on the list”.
How Tester Marketplace fits
You publish a capped campaign with rules; testers participate under those rules and you align invites with Play Console. For a one-off gate, DIY groups may be enough; the marketplace shines when you want to repeat the process across releases with telemetry.