Google Play closed testing: 12 testers for 14 days

Publishing your first Android app involves more than uploading a build. This guide explains the testing threshold and gives you a practical way to organize your test evidence.

Who needs 12 testers?

Google requires personal developer accounts created after November 13, 2023 to complete a closed test before requesting production access. At application time, at least 12 testers must have remained opted in for the preceding 14 consecutive days.

Internal testing is useful for early checks, but does not replace this closed test. Meeting the numbers lets you apply; it does not automatically approve publication.

What does continuous opt-in mean?

A tester who leaves and later rejoins needs a new uninterrupted qualifying period. Adding an email address alone does not establish continuous opt-in. Keep testers informed that they need to remain enrolled.

A practical test plan

The following organization tips are our suggestions, not additional Google requirements. Adapt the tasks to what your app actually does.

1. Choose realistic journeys. For a habit app, try creating a habit, recording progress and editing a reminder. For a photo app, try importing, editing and exporting a picture.
2. Write an invitation people can follow. Include your app name, the purpose of the test, the enrollment link and a contact for problems. Ask testers to confirm which Google account they used if access fails.
3. Prepare a small issue log. Record the app version, device, steps, expected result and actual result. Avoid collecting information you do not need.
4. Review feedback during the test. Group duplicate reports, fix the most disruptive problems first and ask affected testers to try the updated build.
5. Check readiness before applying. Review enrollment in Play Console and summarize the concrete improvements made during testing.

Example: turn a vague report into useful evidence

“It does not work” gives you little to investigate. A better report is: “On version 1.2, I selected a photo, tapped Export and returned to the editor without a saved image.” Add the device and whether the problem repeats. After a fix, record the new version and the tester’s result.

A compact log can use these columns: date, version, test journey, observation, decision and verification result. Leave unknown facts blank rather than inventing successful tests.

What happens after 14 days?

Apply from your Play Console dashboard when eligible. Google asks about tester engagement, feedback, your intended audience and the changes that made the app ready. It can require more testing if engagement or other requirements are insufficient.

Use your own records to answer. For example, describe a navigation problem testers found, the change you shipped and how you checked it. A generic answer copied from another app does not explain your test.

Sources and further reading

The policy summary above follows Google’s official app testing requirements, checked September 7, 2026. Google controls production approval; 12Testeures is an independent guide.

Guides in French: 12 testeurs pendant 14 jours, finding testers and preparing production access.