Google Play closed testing: 12 testers for 14 days

If you opened a personal Google Play developer account recently, the "Production" button is probably greyed out. Google requires a closed test before your first public release, and the rule is strict about the details.

Who has to do it

The requirement applies to personal developer accounts created after November 13, 2023. Organization accounts are outside it. If you are an individual developer and your account is newer than that date, assume it applies to you.

When it launched the rule asked for 20 testers. Google lowered it to 12, and the current Play Console help page says 12.

The rule, word by word

Google's wording is "a minimum of 12 testers who have been opted in continuously for at least 14 days". Each part matters:

• 12 testers with a Google account each. Twelve email addresses on a list is not enough: each person has to opt in.
• Opted in. A tester joins by opening the opt-in link and accepting. The link only appears once the closed testing track is published.
• Continuously for 14 days. If someone opts out on day 9 and opts back in, their count restarts. Testers who leave before day 14 do not count.
• Still opted in when you apply. The 12 have to be there on the day you ask for production access.

Setting up the test

1. In Play Console, go to Test and release → Testing → Closed testing and create a track.
2. Add testers with an email list or a Google Group. Lists accept comma-separated addresses or a CSV file. With a group, testers join the group first and then opt in.
3. Upload a build and send the track to review. Closed tracks are reviewed too, so expect a short wait.
4. Once the track shows as published, copy the opt-in link and send it to your testers. Ask them to install the app from the Play listing it leads to.
5. Count 14 days from the day your 12th tester opted in. Keep a few spare testers in case someone drops out.

What Google looks at

Twelve names on a list is the minimum. When you apply for production you answer a questionnaire in three parts:

• About the closed test: how easy it was to recruit testers, whether they used all the features, and what feedback you got and how you collected it.
• About the app: who it is for, what it does for them and how many installs you expect in the first year.
• About production readiness: what you changed because of the test, and how you decided the app was ready.

Google says the review usually takes seven days or less. It can ask for more testing if fewer than 12 testers stayed opted in or if they barely used the app. Testers who install and never open the app make for a weak answer to that questionnaire.

Practical tips

• Recruit 15 to 20 people. Someone always leaves the group or switches phones.
• Ship an update during the test. A new build with fixes from tester feedback gives you something concrete to write in the questionnaire.
• Collect feedback in writing. A short form or a shared chat is enough, and it is the evidence you summarize later.
• Avoid paid "tester exchange" services that install and forget. Low engagement is one of the reasons Google gives for asking for more testing.
• Use the 14 days for the paperwork. Production access is only the first gate; the listing still needs its privacy policy URL, Data safety form and content rating.

Use the waiting time well

Two weeks of testing is a good window to prepare everything the store listing asks for. Google requires a privacy policy URL that is public and not a PDF, a contact email, and an account deletion link if users can create accounts. The Data safety form guide and the account deletion URL guide cover the two that take the longest.

Lanpage publishes those pages, plus a landing page you can send your testers, on stable URLs you can edit any time. The dashboard checklist shows what is still missing, based on the store rules we follow. Set up your app's pages for free while your testers do their 14 days.