Table of contents
- Quick nav
Google Play Closed Testing: How to Meet the 12 Testers for 14 Days Requirement and Get Production Access
Who this rule applies to
Plenty of indie developers publishing to Google Play for the first time find the Production track greyed out. The reason is Google's testing requirement for new personal developer accounts:
Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Only then can you apply for production access from the Dashboard.
| Account type | Needs the 12-tester, 14-day closed test? |
|---|---|
| Personal, created after 2023-11-13 | Yes |
| Personal, created earlier | Not covered by this rule |
| Organization | Not covered; goes through organization verification instead |
The requirement was originally 20 testers and was later lowered to 12. The wording in your own Play Console is what counts.
The four testing tracks
| Track | Purpose | When available | Counts toward the requirement? |
|---|---|---|---|
| Internal testing | Small trusted group; builds arrive almost instantly | Any time | No |
| Closed testing | A tester list you control | After you complete app setup | Yes |
| Open testing | Anyone can join | After you get production access | — |
| Production | All users | After you meet the closed-test criteria and your application is approved | — |
The most common mistake is running the 14 days on internal testing. Internal testing doesn't count. The test has to be on a closed track.
Step by step
- Complete app setup. Finish the Dashboard tasks: app content, privacy policy, Data safety, content rating, target audience and store listing. You can't start a closed test until they're done.
- Create a closed testing track. Go to Testing → Closed testing, create a track, upload your AAB and roll it out to that track.
- Add testers. Use an email list or a Google Group. Every tester needs a Google account.
- Get testers to opt in. Send the opt-in link. Each tester taps "Become a tester" on the web page, then installs the app from Google Play. Testers who are on the list but never opted in don't count.
- Keep them for 14 consecutive days. When you apply, at least 12 testers must have been opted in continuously for 14 days. A tester who leaves and rejoins starts the count over.
- Apply for production. On the Dashboard, click Apply for production and answer the questionnaire.
The three parts of the application
| Section | What it asks | How to prepare |
|---|---|---|
| About your closed test | How you recruited testers, how engaged they were, what feedback you got | Keep a log of feedback and the fixes that followed |
| About your app/game | Target audience, core features, the value you provide | Use the same positioning as your store listing |
| About your production readiness | What you changed based on testing and how you decided it's ready | List each build you shipped during the test and what changed |
Answer honestly. Shipping a few fix updates during the test, and being able to describe real feedback and changes, makes a stronger case than "12 people installed it and never opened it." If your application is declined, follow Google's feedback, keep testing, and apply again.
Where to find testers
- Colleagues, friends and family, or an existing early-access group
- Your newsletter subscribers or community members
- Reciprocal testing with other developers in dev communities
Testers should actually use the app and give feedback. The questionnaire asks about tester engagement, and Google looks at whether the test was meaningful. Don't rely on anonymous "tester-for-hire" services.
Use the 14 days to finish your store listing
The two-week wait is a good time to polish your store assets, so you can launch as soon as access is granted:
| Asset | Key specs | Reference |
|---|---|---|
| App icon | 512 × 512, 32-bit PNG | iOS & Android icon specs |
| Feature graphic | 1024 × 500, JPG or 24-bit PNG (no alpha) | Feature graphic guide |
| Phone screenshots | 2–8 images; sides 320–3840px; long side no more than 2× the short side | Google Play screenshot requirements |
| Short description | Up to 80 characters | Short and full description guide |
| Full description | Up to 4,000 characters | Same as above |
Your testers' feedback can shape these assets too. The feature they react to first is usually the benefit your first screenshot should lead with. Build the screenshots in a design tool, or export them at Play sizes straight from a browser mockup tool such as AppShot Maker.
Other requirements for new personal accounts
New personal accounts also have to complete:
- Developer identity verification, with details that match your legal name
- Android device verification, which proves through the Play Console mobile app that you have access to an Android device
Both appear as tasks on the Dashboard. Work through them as prompted.
FAQ
| Question | Answer |
|---|---|
| Can internal testing replace it? | No. It has to be a closed testing track |
| Are exactly 12 testers enough? | The rule says at least 12. Recruit a few extra in case someone drops out |
| Can I ship updates during the test? | Yes, and you should, based on feedback |
| What if a tester leaves? | Their streak breaks. You need others who have already reached 14 days |
| Do organization accounts need this? | No, this testing requirement doesn't apply to them |
Summary
If your personal account was created after 2023-11-13, run a closed test, keep at least 12 testers opted in for 14 consecutive days, then apply for production from the Dashboard and answer the questions honestly. Internal testing doesn't count. Use the two weeks to collect feedback, ship fixes, and get your icon, feature graphic and screenshots ready.
Ready to design your store screenshots?
Try AppShotMaker and turn raw captures into store-ready screenshots in minutes.