Who needs a closed test?
Personal developer accounts created after November 13, 2023 need at least 12 testers opted in continuously for at least 14 days before applying for production access.
Start by checking your account type, creation date and app dashboard. Keep this account requirement separate from the other app setup and policy checks shown in Play Console.
What should you check before inviting anyone?
Open your test invitation in a separate browser session before sharing it. A useful invitation tells someone what the app does, how to join, what to try and where to report a problem.
- Confirm that your closed testing release is available to the intended testers.
- If you use a Google Group, supply its join URL separately from the Google Play opt-in URL. Joining the group alone is not the same as opting in.
- Write a short task list around your main user journey. Include a way to report blocked access.
- Use synthetic test data. Arrange limited test accounts through a secure channel when needed.
Which clock are you measuring?
Keep a dated record of invitations, access problems and opt-out reports. Use the calculator for planning, then verify the status shown by Play Console.
| Milestone | What it means | What it does not mean |
|---|---|---|
| Invitation sent | Someone can start joining | They have opted in |
| Qualifying cohort opted in | The continuous period can begin | Approval is scheduled |
| 14 full days elapsed | You may be eligible to apply | Google has approved the app |
| Production access granted | Google accepted the application | Your release has automatically been published |
How can you collect useful feedback?
Give testers tasks with an observable outcome: create a record, edit it, find it again, then recover from a mistake. Ask what they expected and what happened instead. A list of installations cannot tell you why a screen confused someone.
- Record the app version, affected screen and steps to reproduce.
- Separate a blocked task from a cosmetic issue.
- Keep feedback in one place and note the change you made.
- Ask for another attempt after a fix so you can record whether it helped.
How should you handle a dropout?
Identify whether enough continuously opted-in testers remain. Do not add together shorter periods from different people. A larger initial cohort can help, but an extra invitation is not evidence of continuous participation.
If the qualifying group changes, revisit your estimated date. The calculator cannot see tester status or reset itself when someone leaves.
What comes after closed testing?
Review the issues you found, the fixes you made and the tasks testers actually completed. Use that record when preparing your production-access application.
Read the production-access walkthrough for an evidence worksheet. If you prefer help coordinating testers, review the proposed TestPogo plan and its limits first.
Common questions
Does this requirement apply to every developer?
This requirement applies to personal developer accounts created after November 13, 2023. Check your own Play Console for the requirements that apply to your account and app.
What does continuous opt-in mean?
Each qualifying tester must remain opted in without interruption for at least 14 days. A tester who opts out and rejoins needs a new consecutive period.
Does installing the app mean a tester has opted in?
Installation and opt-in are different steps. Ask testers to join your closed test using its opt-in link, then install and use the eligible build.
Does a replacement inherit the previous tester’s days?
No. A replacement has their own opt-in history, so replacing a tester can extend the time before you qualify.
Are daily opens a published numerical requirement?
Google’s cited guide does not prescribe a daily-open count. It asks about engagement and feedback; TestPogo’s proposed daily participation checks are a separate service commitment.
Will production access be approved when the time is up?
No. Meeting the testing requirement makes you eligible to apply for production access. Google reviews your application and may ask for more testing.
Can a calculator confirm eligibility?
No. A calculator only estimates elapsed time from the start you enter. Play Console is authoritative for your eligibility.