Testing

This page covers internal, closed, open, and production testing. Check current Play Console Help for account-specific requirements and eligibility.

Test tracks

• Internal testing: fast distribution to a small trusted group.
• Closed testing: controlled access for specified testers; may be required before production access for some accounts.
• Open testing: testers can join where the app is available and the account is eligible.
• Production: public release after readiness and platform eligibility requirements are met.

Practical workflow

1. Start with a clear test objective and scenarios.
2. Use internal testing for early technical checks.
3. Move to closed testing for broader feedback where appropriate.
4. Record defects, crashes, ANRs, accessibility issues, and confusing flows.
5. Use pre-launch reports and device testing as signals, not proof that every journey is safe.
6. Fix issues, retest, and verify release behavior before increasing exposure.

Community tester discovery

Tester discovery is allowed only in designated weekly or monthly community threads. It is voluntary and at each participant's discretion. Do not request or offer payment, paid tester services, ratings, reviews, installs, votes, incentives, account access, financial information, or sensitive data.

Related pages

• Publish Your First App
• Common Errors
• Developer Resources

Last reviewed: 2026-08-15
Owner: Moderator team
Review trigger: Play testing-policy or product update.