Google Play Production Access

Testing is a prerequisite for some accounts

For developer accounts subject to the rule, the closed testing prerequisite is a condition of applying: a minimum number of testers who remain opted in for a continuous period. The figure most commonly cited is 12 testers for 14 continuous days.

Because Google sets and revises this policy, confirm the current requirement for your account type before planning a window. The Play Console Help centre is the authoritative source.

Why Google asks for testing at all

The requirement exists to filter out apps that have never run outside a developer's own device. A closed test demonstrates that the app has been installed and used by other people, on other hardware, for a sustained period.

That framing is useful when preparing an application, because it tells you what the record needs to show: real testers, real installs, a real window, and enough continuity to be credible.

Participation you can stand behind

The temptation is to describe the campaign at its best moment: the day the full roster had opted in. The safer approach is to describe the period as it actually ran, including the days when it dipped.

• State opted-in testers, and keep invitations out of the number.
• Describe the window continuously, including whether the count ever fell below the threshold.
• If testers were replaced, say so and give the dates.
• Use the same figures as your campaign record, so the description and the evidence agree.

Preparing testing feedback

Feedback is what turns 'we tested' into 'here is what testing found'. It does not need to be extensive; it needs to be genuine and attributable.

• Group findings by the build they were raised against, so it is clear what was fixed when.
• Note the device and Android version where the finding occurred.
• Record what changed as a result, including findings you decided not to act on and why.
• Keep the raw record. A summary nobody can trace back is weaker evidence than a list with dates attached.

Contents of the summary

• The testing window, with exact start and end dates
• Testers opted in, and how many were invited, kept as separate figures
• The number of continuous days the count stayed at or above the threshold
• Any interruption, its date, and what caused it
• The builds tested, and the findings raised against each one

If a figure in your application would not be traceable to a date in this summary, that is a sign the campaign was not recorded closely enough while it was running.