Google Play closed testing: the complete guide

Closed testing on Google Play lets a limited group of testers install your app before it goes public. For some new developer accounts it is also a required step before you can apply for production access. This page sorts the questions by situation and points to the right guide.

Requirement box (verified 2026-10-17). Google Play Console Help states that personal developer accounts created after November 13, 2023 must test first, with "a minimum of 12 testers who have been opted in continuously for at least 14 days". Source: Play Console Help, retrieved 2026-10-17. Policies change; check the page before you plan.

Guides

• Do tester reviews count toward your public rating? Feedback from test users does not affect the public rating and testers cannot post public reviews for test versions.
• Does your Google Play developer account need a closed test? How to check whether the closed-test requirement applies to you, by account type and creation date.
• Google Play closed test requirements for new accounts Which accounts must run a closed test, how many testers and days are required and what counts, with the official source.
• Google Play tester limits per track: internal, closed, open The official limits side by side so you can plan the right track.
• What counts as 14 days in a Google Play closed test Opted in for 14 continuous days: what that means, what happens when a tester leaves and how to count your own days.
• What to do during the 14 days of a closed test A day-by-day plan: day 1 setup, mid-test check-ins, final days and how to keep the log for your application.

Fix a problem

• Closed test opt-in link not showing: what to check The opt-in link appears only for a published test status. Check status, list assignment and review state.
• Testers cannot find your app after opting in Typical reasons a tester cannot install: wrong account, group not joined, track state or device rules.