Latest update
Testers tried signing in and saving notes. One finding reports difficulty retrying after a lost connection.
GOOGLE PLAY CLOSED TESTING
Closed testing for Android apps.
Submit your Google Play testing link, track opt-ins and testing days, and collect feedback before applying for production access.
From USD 8.99From a single test run
The one-time plan includes 14 testers, 14 primary devices plus 2 reserve devices, and a 16-day schedule.
Support for up to 3 retests
Track test progress
View full-size screenshot
See recorded days, opted-in testers, and devices in use for each app.
Actual interface · Sample dataScreenshots show the Vietnamese interfaceHow a closed test works
From setting up a Play Console track to reviewing feedback before release.
Choose a plan
Pick a one-time run, or a monthly or yearly plan for more projects.
Submit your Play link
Enter the app package name and the closed-test opt-in link from Play Console.
Track days and testers
Open your private tracking link to see the progress recorded by the testing coordinator.
Review the findings
Use feedback to improve your app and apply for production access in your Play Console.
Prepare your Play Console track
Use your developer account to create a closed track, release a build and share the opt-in link.
Read the Google setup guideCreate a closed test
Open Closed testing in Play Console and create a release with your Android App Bundle.
Give your testers access
Choose a list of email addresses or a Google group. Testers use an account that has been granted access.
Share the opt-in link
After releasing your build, copy its opt-in link from Play Console and include it in the testing request.
For personal developer accounts created after November 13, 2023, Google requires at least 12 testers to stay opted in continuously for at least 14 days before applying for production access.
Explore the testing dashboard
Choose a section to see the daily log, devices, and findings from a sample test.
Test overview
Field Notes v1.4.0 (48)
- Recorded days
- 816
- Opted-in testers
- 14
- Participants in this example
- Recorded device models
- 3
- Google Pixel, Samsung, and Xiaomi
What to test again
Check that Retry appears when the connection returns and that users can finish signing in.
Daily testing log
Choose a day to see details from the sample test.
- Recorded
- Testing
- Scheduled
Day 9
In progressThe team is checking draft saving and investigating feedback about slow sync status updates.
Devices in this test
Device models and recorded statuses for this test.
| Brand and model | Android version | Status |
|---|---|---|
| GooglePixel 8 | Android 15 | Tested |
| SamsungGalaxy A54 | Android 14 | Testing |
| XiaomiRedmi Note 12 | Android 13 | Assigned |
Test findings
Open a finding to see how to reproduce it and what happened.
Sign-in is hard to retry after losing connectionHigh
- Steps to reproduce
- Open the sign-in screen, turn off Wi-Fi, and submit the form. Restore the connection on the error screen.
- Observed result
- The error stays on screen and the tester has to go back to submit the form again.
The keyboard covers the Save buttonMedium
- Steps to reproduce
- Create a note in portrait mode, enter several lines, and leave the keyboard open.
- Observed result
- The Save button appears after the keyboard closes.
Saving a note has no visible confirmationLow
- Steps to reproduce
- Edit a note and tap Save.
- Observed result
- The app returns to the list without a save confirmation.
Prepare for Play Console
Use your app’s logs and findings to prepare an application for production access.
- Your closed test
- Record how you recruited testers, what they tried, and how you collected feedback.
- Your app and its audience
- Describe who the app is for, the problem it solves, and your estimated installs.
- Readiness for release
- Connect findings to your fixes, the build that includes them, and how you verified the changes.
Verify the eligibility and opt-in period in Play Console. Google reviews applications for production access.
Request a retest
Use this process if Google requests further testing after the original test.
- Share Google’s notice
Include the package name, the Play Console notice, and a link to the active test.
- Update the build
Address the reported issue and tell the testing team which build to test next.
- Follow the next round
The team reviews eligible requests and helps you follow the results of the next test.
Up to 3 additional testing rounds are available for the same package on eligible requests.
Inside the customer dashboard
Open an app’s report to see what was tested and plan the next update.
Actual interface · Sample dataScreenshots show the Vietnamese interface
View customer dashboard screenshots
Daily testing log
See how many testers participated and which app workflows were tested each day.
View full-size screenshot
Devices by brand
See device brands, models, Android versions, and which devices are in use.
View full-size screenshot
Findings you can reproduce
Review severity, reproduction steps, and observed results to plan your next fix.
View full-size screenshotChoose a testing plan
Book one test run or select a monthly or yearly plan.
Billing currency: USD
One-time
One round of closed testing.
USD 8.99 / One-time
- 16 days
- 14 devices
- 2 reserve devices
- 14 users
- 1 apps
- Support for up to 3 retests
Pro
For developers managing several releases.
USD 12.99 / per month
- 30 days
- 42 devices
- 6 reserve devices
- 42 users
- 3 apps
- Support for up to 3 retests
Premium
For teams testing more apps and devices.
USD 24.99 / per month
- 30 days
- 70 devices
- 10 reserve devices
- 70 users
- 5 apps
- Support for up to 3 retests
The one-time plan includes 14 testers, 14 primary devices plus 2 reserve devices, and a 16-day schedule.
Tester, device and app counts are plan capacity limits. Requests are reviewed before scheduling. Test checkout uses simulated transactions.
Payment methods
- VISA
- PayPal
- Vietnam bank transfer
- Digital wallets
Compare every plan
See capacity, reporting and support for all three plans. Scroll sideways on a small screen to see every column.
| Feature | One-timeUSD 8.99One-time | ProPopularUSD 12.99per month | PremiumUSD 24.99per month |
|---|---|---|---|
| Tester capacity & duration | |||
| Tester capacity | 14 | 42 | 70 |
| Apps per plan | 1 | 3 | 5 |
| Plan duration | 16 days | 30 days | 30 days |
| Devices & coverage | |||
| Devices in plan | 14 | 42 | 70 |
| Reserve devices | 2 | 6 | 10 |
| Track by brand, model and Android version | Based on assigned devices | Based on assigned devices | Based on assigned devices |
| Evidence & reporting | |||
| Private per-app reports | Included | Included | Included |
| Print or save reports as PDF | Included | Included | Included |
| Feedback, severity and reproduction steps | Included | Included | Included |
| Links to screenshots, videos or documents | When evidence is available | When evidence is available | When evidence is available |
| Progress tracking | |||
| Daily activity log | Recorded by the test coordinator | Recorded by the test coordinator | Recorded by the test coordinator |
| Recorded days and enrolled testers | Recorded by the test coordinator | Recorded by the test coordinator | Recorded by the test coordinator |
| Support & retests | |||
| Production access questionnaire guidance | Included | Included | Included |
| Retest when Google asks for more testing | Up to 3 eligible retests | Up to 3 eligible retests | Up to 3 eligible retests |
| Price & billing | |||
| Billing interval | One time | Monthly or yearly | Monthly or yearly |
| Total billed for the selected term | USD 8.99One-time | USD 12.99per month | USD 24.99per month |
| Yearly savings | — | 10% | 20% |
| Choose a testing plan | |||
RETEST SUPPORT
Google asked for more testing? We’ll help run up to 3 retests.
Share your Play Console notice in your Zovatesting account. Our team reviews the request and activity log, then helps plan another test for the same package.
- Daily activity log
- Reports with reproduction steps
- Production access guidance
Frequently asked questions
What to prepare and how your request is handled.
What does Google Play require?
For personal developer accounts created after November 13, 2023, Google requires at least 12 testers to stay opted in continuously for 14 days before you can apply for production access.
What information should I submit?
Provide the app name, package name and closed-testing opt-in link, plus any flows you want tested. Keep your Play Console password and signing keys in your account.
How can I follow my request?
Save the private link shown after submission. It shows the testing status, days, opted-in testers and reports once the coordinator adds updates.
What if Google asks me to test again?
Submit a request in Reports. We review the Play Console feedback and help with up to 3 eligible retests for the same app after its initial test.
Who decides production access?
Once you meet the testing requirements, you can apply for production access. Google reviews that application. Publishing your release on Google Play has a separate review process.
Resources and support
Read the official guides, review our terms and check your requests in your account.
Ready to set up your closed test?
Choose a plan, then send the app package name and closed-testing link.