Google Play 14-Day Closed Testing Requirement Explained
Who needs a closed test, the 12-tester and 14-day rules, and how to answer the production questionnaire.
Read the guide →How to Get 12 Testers for Google Play Closed Testing
If your Play Console shows Production as locked, you have probably reached the closed testing requirement. New personal developer accounts need at least 12 testers who stay opted in for 14 days before an app can go live. This guide covers where developers find those testers, what can go wrong, and how to choose the option that fits your app.
Why Google asks for 12 testers
Google requires personal developer accounts created after November 13, 2023 to run a closed test before they can publish to production. The test needs at least 12 testers opted in, and each tester has to stay opted in for 14 consecutive days. The idea is that real people try your app before it reaches everyone.
Until you meet these criteria, the Production and Pre-registration options in Play Console stay locked. You can read Google's own description on the Play Console Help page.
What counts as a tester
A tester is a real person with a Google account who opens your opt-in link, joins the test and installs the app. Three details decide whether they count:
- They must opt in. Adding an email address to your tester list is not enough. The person has to open your opt-in link and join.
- They must stay opted in for 14 days in a row. Someone who joins, tests for a few days and then leaves does not count. If a tester leaves and rejoins, the count can be broken.
- They should actually use the app. The production questionnaire asks how testers engaged with your features and whether their usage looked like real users.
Five ways to find 12 testers
1. Friends and family
This is free and fast to start. The problem is follow-through. Many people install the app once and forget it, and some uninstall it or leave the test. Expect to send reminders.
2. Colleagues, classmates and your network
A wider circle helps you reach 12 faster. Ask people to use a Google account they check, and explain clearly why they must stay opted in for 14 days.
3. Developer communities
Many developers join groups on Reddit, Discord or Facebook where members test each other's apps. These swaps work, but you owe time in return and you depend on strangers staying active.
4. Your own audience
If you have a newsletter, a waitlist or social followers, invite them. They match your real users, which makes them useful testers. You need an audience first, though.
5. A testing service
A service gives you a ready team of testers on real devices who test daily for the full period. It costs money, so check what you get: real people on physical devices (not emulators or bots), how long they test, whether you receive feedback, and whether you get help with the production questionnaire.
Mistakes that break or weaken your test
- Testers who never opted in. Having an address on the list is not the same as joining the test.
- The wrong Google account. The email on your list must be the account the tester uses on their Android device.
- Exactly 12 testers. If one person drops out, you fall below the limit. Aim for a few extra.
- Testers leaving early. Tell everyone to stay opted in for the full 14 days.
- One-time installs. Testers who open the app once and never return give you little real feedback. Ask for specific tasks.
- No feedback channel. Testers cannot leave public Play Store reviews for test versions, so add a feedback email or link on the opt-in page.
How to keep testers active
Send a short message at the start with the opt-in link, the date until which they must stay opted in, and two or three things to try. Remind them every few days. Collect feedback in a form or a shared chat, then fix what you find and release an update. Google's questionnaire asks which changes you made based on testing, so real fixes make that answer easy to write.
Tip: Keep a simple sheet with each tester's name, email, opt-in date and last check-in. It shows you quickly who has dropped out.
Should you use a testing service?
If you have a small network or a tight launch date, a service can save weeks. If you have an audience and time, recruiting testers yourself costs only effort. A fair rule: do it yourself if you can name 15 reliable people today, and use a service if you cannot.
12AppTesting provides 12, 15 or 20 real Android testers on physical devices, with no bots and no emulators. Testing runs daily for 14 days with 7 extra days of support, and packages start at $7. You add our tester list to your closed test, send us your testing link, and we handle the rest. See the packages and prices.
Quick checklist
- Your account was created after November 13, 2023, so the requirement applies
- You have 15 or more testers lined up
- Your closed testing track exists and a release is rolled out
- Testers are added and have your opt-in link (see how to add testers)
- Every tester has opted in and installed the app
- Reminders are planned for the 14 days
- A feedback channel is set up
- After day 14, you apply for production (see the requirement explained)
Rules can change. Check Google's current Play Console Help page before you start.