Google Play closed testing service
Get 12 testers for 14 days of Google Play closed testing.
Coordinate Android app testers, share your testing instructions, follow progress, and review a closeout report in one workspace. Compare managed testing plans and prepare your app for the next step.
Built around the closed-test requirement, with responsibility for your app and store submission remaining with your team.
Before the release window opens
Start with a release question and a team ready to answer it.
- The build, Play Console closed-testing link, and app access instructions are ready before the clock starts.
- The testing brief names the journeys and questions that testers should explore.
- Your team knows who can respond if a participant cannot access or use the app.
- You understand that completing a test lets you apply; Google makes the production-access decision.
The release method
Three deliberate moments. One accountable release thread.
Rather than treating the requirement as a disposable formality, keep the brief, the working window, and the closeout connected.
01 / Prepare
Register your Android app
Share the package name, closed-testing link, access instructions, and the important journeys testers should explore.02 / Coordinate
Track the 14-day test
Follow tester participation, access questions, daily progress, and feedback from one shared workspace.03 / Close out
Review feedback and next steps
Finish with an organised testing record and guidance for the production-access application in Play Console.Choose release support
Clear support options. No subscription.
Choose the appropriate scope for the releases you are preparing. A live offer is clearly marked when one is active.
Basic
1 credit for 1 app
- 1 credit - covers 1 app submission
- 14 verified testers
- 16 calendar days of testing
Premium
2 credits for 2 apps
- 2 credits - covers 2 app submissions (1 credit = 1 app)
- 14 verified testers
- 16 calendar days of testing
Set expectations clearly
Separate the platform rule, the release work, and the decision boundary.
The platform baseline
12 opted-in testers for 14 continuous days
Affected personal developer accounts must meet this Google Play closed-test condition before they can apply for production access.The managed test
Real testers, a visible window, and a useful closeout
The service coordinates the work around the requirement: app access, tester participation, feedback, progress, and reporting.The responsibility boundary
No testing service can promise production access
The service supports release preparation. Google independently reviews the account, app, listing, policies, and production-access request.Your release sequence
Keep each handoff visible enough to own.
- 01
Frame
Write the release brief
Set out the build, closed-testing link, access path, and release question before the working window opens. - 02
Open
Coordinate one testing window
Make the opt-in route, access instructions, ownership, and timing visible so the team does not solve the same handoff twice. - 03
Read
Follow the release signals
Use one workspace to follow milestones, retain notes, and surface access or product questions while there is still time to respond. - 04
Decide
Keep the decision record
Close with a clear record of the release context, participation, and available observations for the people deciding what comes next.
Release resources
Use the material that helps your team take the next step with confidence.
Fix tester access problems
Check the account, invitation, release, and device in a practical troubleshooting order.
Open resourcePrepare your production application
Use your own feedback and fix history to explain what you tested and changed.
Open resourceSample testing report — illustrative
See an example activity log, issue list, and handoff checklist. This is a sample, not a customer result.
Open resourceSet up your closed test
Prepare your release, invite testers, and organise useful feedback.
Open resourceChoose the peer route
A self-directed option for developers who want to build and coordinate their own testing circle.
Open resourceGuidance reviewed November 1, 2026.
Questions, answered
Before you open the release window.
Completing a closed test allows an affected account to apply. Google alone makes the production-access decision.
Can I hire Android app testers for Google Play closed testing?+
Yes. Choose a managed closed-testing package if you want help coordinating Android app testers, sharing access instructions, tracking participation, and collecting feedback. Compare the current package tester count, duration, and app submissions before ordering. Google independently reviews production-access applications.
What does managed closed-testing support cover?+
A package helps the release owner prepare the closed-test handoff, coordinate an accountable working window, and retain a useful release record. See the pricing page for the current package scope before you begin.
Can I use the free community instead?+
Yes. The public community is a self-directed route for developers who want to organise peer testing themselves. Managed support is for teams that want an explicit release brief, working window, and closeout around a particular launch.
What is the 12-testers-for-14-days requirement?+
For affected personal Google Play developer accounts, Google requires a closed test with at least 12 testers opted in continuously for the last 14 days before the account can apply for production access. Check Google Play's current guidance for eligibility and the latest wording.
What should I prepare before a closed test starts?+
Have a usable build, the correct Play Console closed-testing link, access instructions, a named release owner, and a short brief explaining the release question or journeys the window should cover.
What if participation changes during the window?+
Check the status in your own Play Console and clarify the next action early. If someone has trouble with access or participation, resolve it promptly and keep the release owner’s record up to date.
Does the service guarantee Google Play production access?+
No. 12 Testers 14 Days coordinates the closed-testing process, but Google independently decides whether an account receives production access.
Does internal testing count toward the 12 testers requirement?+
Google distinguishes testing tracks in Play Console. For the production-access requirement, check the current Google Play guidance and make sure your team is using the appropriate closed-testing track.
When can I apply for production access?+
Use the status and eligibility information shown in your Play Console account, alongside Google's current documentation, to understand when your account can apply and what details Google will ask for.
What should a closeout give the product team?+
A useful closeout captures the testing scope, what was observed, any important feedback, and the next release decision. It should help your team avoid starting from scratch when the next question appears.
Is free community testing available if I am not ready to buy a package?+
Yes. You can use the community hub to meet volunteer testers and organise a run yourself. It is intentionally self-managed and does not provide the structure or support of a managed package.
When the build is ready