Quick answer
Google Play closed testing is a release track for sharing your app with selected testers and collecting private feedback before a wider release. For personal developer accounts created after November 13, 2023, it also unlocks production: at least 12 testers must be opted in when you apply, and each must have stayed opted in for the preceding 14 days. Meeting that lets you apply for production access; Google still reviews the application.
Source: Play Console Help, answer 14151465, checked October 9, 2026.
Who needs to run a closed test?
Every developer can use closed testing, but one group must pass it before publishing: personal developer accounts created after November 13, 2023. For them, each new app needs a closed test with at least 12 continuously opted-in testers before the production application unlocks.
Google's wording
At least 12 testers must be opted in to your closed test when you apply for production access, and they must have been opted in continuously for the preceding 14 days.
Must pass the test
- A personal developer account created after November 13, 2023
- Each new app you want to publish from that account
- At least 12 testers, each opted in for the 14 days before you apply
Outside this rule
- Organization accounts (Google writes the rule for personal accounts)
- Personal accounts created before the November 13, 2023 cutoff
- Updates to an app that already has production access
Outside the rule does not mean outside review: every app still goes through Google's normal checks. When in doubt, open the app's Dashboard in Play Console. It shows whether the testing task applies to that app.
Google introduced the rule in November 2023 at 20 testers and lowered it to 12 on December 11, 2024. Tutorials that still ask for 20 describe the old rule (what changed from 20 to 12). The test is per app, so a second app needs its own (do you need 12 testers for every app), and the full qualification rules live in the 12-tester requirement explained.
Closed, internal or open testing: which track do I need?
Internal testing is for quick checks with up to 100 people and does not satisfy the production requirement. Closed testing is the track that counts. Open testing is a public beta, and for affected personal accounts it only becomes available after production access is granted.
| Track | Best for | Who can join | Capacity | Counts for the 12-tester rule |
|---|---|---|---|---|
| Internal | Best forQuick checks with your own team | Who can joinTesters you add by email | CapacityUp to 100 per app | Counts for the 12-tester ruleNo |
| Closed | Best forFeedback from people you choose | Who can joinEmail lists or Google Groups you select; each person opts in | CapacityEmail lists of up to 2,000 people, up to 50 lists per track | Counts for the 12-tester ruleYes, this is the qualifying track |
| Open | Best forA public beta | Who can joinAnyone who joins from your store listing | CapacityUnlimited, or a cap of at least 1,000 | Counts for the 12-tester ruleNo; opens after production access for affected accounts |
Limits from Play Console Help, answer 9845334. The full side-by-side, with screenshots and review behaviour, is in internal vs closed vs open testing.
Which testing track fits my next step?
Two questions. It only reads your answers, never your Play Console.
Pick a goal to see which track fits.
Start with closed testing
Closed trackClosed testing is the track Google checks for the production requirement, and it is the right place for feedback from people you choose. Check the requirements shown for your app in Play Console, then set up the test.
Set up closed testing and invite testers · What the 12-tester rule needs
Start with internal testing
Internal trackInternal testing suits quick checks with up to 100 testers. It does not complete the closed-test task: if your Dashboard shows that task, you still need a closed test after this.
Open testing fits
Open trackOpen testing suits a public beta. Check that Open testing is available for this app in Play Console and complete any remaining setup tasks. For affected personal accounts, production access must be granted first.
Closed testing comes first
Closed, then openIf your app's Dashboard shows the closed-testing task, open testing becomes available after production access. Run the closed test, apply for production access, then set up a public beta once access is granted.
Check your app's Dashboard first
Look it upWhich tracks you can use depends on your account type and your app. The Dashboard in Play Console lists any testing task that applies, so start there and come back with what it shows.
A recommendation from your answers, not a check of your account. Your app's Dashboard in Play Console is the final word.
How do I set up a closed test in Play Console?
Finish the app setup, create a release on the closed track and get it through review, add testers with an email list or a Google Group, then share the opt-in link. Nothing counts until testers have opted in.
Finish the app setup
Complete the store listing, the App content declarations (including Data safety) and the other tasks on the app's Dashboard. A release cannot reach testers while setup is incomplete.
Open the closed track
In Play Console go to Test and release > Testing > Closed testing, then choose Manage track on an existing closed track or create a new one.
Create a release
Upload your signed Android App Bundle (.aab), add release notes, and fix anything Play Console flags. A saved draft is not yet available to testers.
Send it for review
Submit the changes from Publishing overview. Google says processing "can take a few hours or up to seven days (or longer in exceptional cases)". Testers cannot install until the release is available.
Choose your testers
On the track's Testers tab, select an email list or add a Google Group address, set how testers send feedback, and save.
Check countries and devices
Testers join from their Play country, so the track must be available where they are. Devices you exclude in Console, or that your build does not support, cannot install.
Share the opt-in link
Copy the link from the Testers tab. Each tester opens it with the invited Google account and taps Become a tester. Google Group members must join the group first. A new link can take a few hours to start working.
Testers install from Google Play
After opting in, testers install from the Play Store and use the app. A closed test for an app that is not yet public does not show up in Play search, so always share the link directly.
Screenshots, the email list versus Google Group decision and the tester messages are in how to set up closed testing and invite testers. Group problems have their own fixes: Google Group closed testing not working.
Paths and review wording from Prepare and roll out a release, Set up an open, closed or internal test and Publishing overview, checked September 27, 2026.
What counts during the 14 days?
Google counts testers who are opted in, and every tester's 14 days are their own. Adding an email only makes someone eligible, and a replacement tester starts a fresh 14 days. Google publishes no minutes-per-day quota, but the application asks how testers engaged and what they reported.
- 01 Added to your list Eligible to join. Not counted yet.
- 02 Opted in Counted from this day. Their streak starts.
- 03 Installed and using Real use and feedback: what your application describes.
- 04 14 days in a row Qualifies, as long as they are still opted in when you apply.
Example: 14 testers join together and two leave early. The remaining 12 can still qualify if they stay opted in throughout the required period. If only 11 remain, a new tester cannot inherit a departed tester's days.
- Opting out breaks that tester's streak. If they rejoin, their 14 days start again from the rejoin day.
- A replacement does not inherit anyone's days. Swapping in a new tester keeps your count up, but that person needs their own 14 days, which can move your earliest application date.
- Updates are expected. Google tells developers to keep running closed tests while fixing reported issues, and does not describe an update as resetting testers' opt-in. Keep your testers enrolled while you ship fixes.
- There is no published daily-use rule. Google names no minimum minutes or sessions. Give testers real tasks and keep a record of what they found and what you changed.
How the streak is counted day by day: does it have to be the most recent 14 days. Invited but not counted: added 12 testers but 0 opted in. Shipping builds mid-test: does updating reset closed testing.
Can someone run the test for me?
Recruiting testers and coordinating their participation takes time. You can organize the test yourself or use a managed service while keeping control of your app, Play Console and production application.
| Recruiting your own testers versus a managed service | Do it yourself | PrimeTestLab |
|---|---|---|
| Finding 12 people | Do it yourselfFriends, communities, tester swaps | PrimeTestLabOnboarding starts within 4-6 hours after setup is complete and the app is accessible |
| Keeping them opted in | Do it yourselfYou check the count and chase people | PrimeTestLabMonitored daily for all 14 days |
| When someone drops | Do it yourselfRecruit again; their days start over | PrimeTestLabReplaced the same day; larger plans add a buffer above 12 |
| Devices | Do it yourselfWhatever your testers own | PrimeTestLabReal Android devices, no emulators |
| Your Play Console | Do it yourselfYours | PrimeTestLabStill yours: no access needed |
Recruiting your own is free and works if you have a reliable group: 7 legit ways to get 12 testers compares the options.
Plans
One payment per app · +5% service fee at checkout, minimum $1.50 · Visa and Mastercard, processed by Stripe
After the full test, an eligible testing-related rejection qualifies for a free retest or refund. Send Google's official rejection email within 14 days of the notice. Unrelated content-policy rejections are excluded. Refund policy and conditions.
How long does closed testing take?
The test itself is 14 days per tester, but it sits between separate Google reviews: the first release, the production-access application and your production release. Google gives no single end-to-end time, so nobody can honestly promise a launch date.
| Stage | What Google says | How to plan for it |
|---|---|---|
| Release review | What Google saysProcessing "can take a few hours or up to seven days (or longer in exceptional cases)" | How to plan for itTreat it as its own wait. Recruiting can start, but nobody can install yet. |
| Opt-in link | What Google saysA newly published testing link can take a few hours to start working | How to plan for itOpen the link yourself before sending it to testers. |
| The qualifying test | What Google saysAt least 12 testers opted in continuously for the preceding 14 days | How to plan for itCounted per tester from their opt-in; replacements start fresh. |
| Production-access review | What Google says"Review usually takes seven days or less, but can occasionally take longer." | How to plan for itAnswer the questionnaire from real testing records. |
| Production release | What Google saysAccess approval lets you publish; the production release is still reviewed | How to plan for itApproval is not a live listing: you still roll out to production. |
Quotes from Publishing overview and App testing requirements, checked October 9, 2026.
Every review stage in detail: Google Play review time in 2026.
Why is my closed test stuck?
Most stuck tests sit in one of a few states: testers invited but not opted in, a release still in review, an app that is not available for the tester's account, country or device, a streak broken by someone leaving, or an application that needs more testing. Find your symptom below.
Symptom
Testers were added, but fewer (or zero) show as opted in
First check
Adding an email is not opting in. Each tester must open the link with the invited Google account and tap Become a tester.
Full fix: Added testers but 0 opted inSymptom
A tester is already in your internal test
First check
Someone opted in to your internal test cannot join the closed test. Google's instruction: opt out of the internal test first, then open the closed-test link.
Full fix: Internal testing setupSymptom
A tester sees "App not available" or "Item not found"
First check
Check that the release is published, the account is on the list, and the track covers their Play country and device.
Full fix: App not available to testersSymptom
Google Group members cannot join
First check
Members must actually join the group before they opt in. An invited address is not yet a member.
Full fix: Google Group closed testing not workingSymptom
The release is still in review
First check
Nothing reaches testers until review finishes. Sending new changes while one is pending can change your place in the queue.
Full fix: Google Play review timeSymptom
"Not available in your country"
First check
Testers join by their Play country. Add their country to the closed track, and check whether the track follows your production countries.
Full fix: Testers in different countriesSymptom
The day counter stopped or went back
First check
Each tester's streak is separate. Find who opted out, and when, before assuming the whole test reset.
Full fix: Closed testing days not updatingSymptom
"Apply for production" is missing
First check
It appears on the app's Dashboard once 12 testers each have 14 continuous days. Check the Dashboard of the right app.
Full fix: Apply for production not showingSymptom
Google asked for more testing
First check
Read the decision closely. Improve the test and your evidence before you reapply, rather than simply waiting again.
Full fix: More testing required: how to reapplySymptom
Will an update reset my 14 days?
First check
Google encourages fixes during testing and does not document an update as resetting opt-in. Keep testers enrolled.
Full fix: Does updating reset closed testingHow do I apply for production access?
When at least 12 testers have each been opted in for the preceding 14 days, Apply for production appears on the app's Dashboard. The form has three sections and Google reviews it, so approval is not automatic.
About your closed test
- How you recruited testers
- How easy it was to recruit them
- How testers engaged with your app
- A summary of the feedback you received
About your app or game
- Who the app is for
- What value it gives users
- How many installs you expect in the first year
About your production readiness
- What you changed based on the test
- How you decided the app is ready
Answer from real records: what testers did, what they reported and what you changed. Google publishes no scoring formula, and a copied answer cannot stand in for a test that happened. Worked examples for every question: production access questionnaire answers. If the answer is no: why closed testing gets rejected.
Approval is permission, not publication. After access is granted you still create a production release under Test and release > Production and roll it out.
Questions developers ask about closed testing
What is Google Play closed testing?
Closed testing lets you share a test version of your Android app with people you choose through Google Play. They try its features and send feedback before a wider release. Their feedback stays private and does not affect your public rating, and you control who can join with email lists or Google Groups.
Do I need 12 testers or 20, and does this rule apply to me?
Twelve. Google reduced the minimum from 20 testers to 12 on December 11, 2024. The rule applies to personal developer accounts created after November 13, 2023. Organization accounts and older personal accounts fall outside that stated scope. Tutorials that still ask for 20 describe the old rule.
I added 12 emails. Why does Google show fewer opted-in testers?
Adding an email makes that account eligible; it does not enroll anyone. Each person must open your test link with that Google account and tap Become a tester. Ask testers which account they used. For an app that is not public yet, share the link directly, because Play search will not find it.
What is the difference between internal, closed and open testing?
Internal testing shares an early build with up to 100 people you add. Closed testing gives people you choose access for targeted feedback, and it is the track that counts for the 12-tester rule. Open testing lets anyone join from your store listing. Some internal releases still need review, such as a first release.
If someone joins my Google Group, are they already a tester?
No. Group membership and test enrollment are separate steps. Add the group address to your closed track and save, then each person joins the group first and opens the opt-in link second. Tell testers to use the same Google account for both steps, or the opt-in will not match.
What happens if a tester leaves before the 14 days finish?
Their interrupted time does not count toward the continuous requirement. When you apply, at least 12 testers must each have the preceding 14 days without opting out. A replacement does not inherit another tester's days, so your earliest application date depends on the testers who stayed, not on how many were ever invited.
Can I update my app during closed testing without starting again?
Yes, updates are part of testing. Google tells developers to keep running closed tests while fixing issues, and the rule is about testers staying opted in. Keep your testers enrolled while you ship fixes. Separately, sending new changes while a review is pending can extend that review.
Can my testers live in different countries?
Yes. Configure the closed track so it is available in your testers' countries. Google uses each person's Play country, not their physical location, for country targeting. Testing countries usually follow your production settings, and you do not need to enable every country just to run a closed test.
Why does a tester see "App not available" or "Item not found"?
Those messages have no single cause. Check that the release is published and the tester's account is on the list, then confirm country availability and device compatibility, since a phone can be excluded in Console or unsupported by the build. Diagnose the exact account and device before uploading another build.
How long will it take until my app is live?
The 14-day test is only one stage. Allow time for app setup, the release review, recruiting testers, the qualifying test, the production-access review and your production release. Google gives separate timing statements for its reviews, so finishing 14 days does not set a launch date or publish the app for you.
Must every tester open the app every day for a certain number of minutes?
Google's published requirements name no daily opening quota and no minimum minutes. They do ask about tester engagement, the features tested and the feedback you received. Give testers realistic tasks, ask them to report problems, and keep honest records of what they tested and what you improved.
Do I need another closed test for every new app?
For an account inside the rule, plan for yes. Google sets up testing and production access per app, and publishing one app does not unlock the next. Check each new app's Dashboard. Later versions of an app that already has production access follow the normal update process.
Can PrimeTestLab handle the testing without accessing my Play Console?
Yes. PrimeTestLab supplies real people on real Android devices without needing access to your Play Console. Onboarding starts within 4-6 hours after setup is complete and the app is accessible to testers. This is the start of onboarding, not a promise that everyone has opted in by then. Each tester's 14-day qualifying period starts from their own opt-in. After the full test, an eligible testing-related rejection qualifies for a free retest or refund. Send Google's official rejection email within 14 days of the notice. Unrelated content-policy rejections are excluded; the other eligibility conditions are in our refund policy.
Bottom line
Closed testing is a normal Google Play track, and for personal accounts created after November 13, 2023 it is also the gate to production: at least 12 testers, each opted in for the 14 days before you apply. Set it up once, keep every tester opted in, answer the application from real records, and treat each Google review as its own step.
Google documentation, checked October 9, 2026