ClosedTest12 testers isn't the goal. Real testing evidence is.
ClosedTest coordinates real Android testers through the full testing workflow: opt-in, daily check-ins, app usage, screenshots, written feedback, bug reports, device coverage, QA findings, and final testing reports.
✓ Opt-in link only · ✗ No Play Console password or account access required
Real testing infrastructure, not invented numbers.
These public metrics are calculated from the ClosedTest testing database. They are intended to show the scale of the tester network and the testing evidence already recorded.
Metrics update from the testing database. Private customer and tester identities are not published.
We do more than put testers on your app.
A useful closed test needs evidence over time. ClosedTest organizes the work around the same operational records your project dashboard uses.
Daily tester check-ins
Track participation across the testing window instead of waiting until the end to discover that testers stopped using the app.
Learn more →Screenshots and written feedback
Tester submissions can include screenshots, feedback, and issue descriptions that remain attached to the testing record.
Learn more →Structured QA findings
Turn tester observations into bugs, UX findings, crashes, severity levels, expected results, and actual results.
Learn more →Device and Android coverage
Track the device models and Android versions represented in the tester network and use them when choosing project coverage.
Learn more →Tester replacement
When a participant drops out, the operational workflow can replace testers so the project does not depend on one fragile tester list.
Learn more →Final testing report
Bring engagement, check-ins, QA findings, device coverage, and recommendations together in a final project report.
Learn more →Why recruiting testers is only the beginning.
The difficult part is maintaining a useful testing process for the full window: keeping participation organized, collecting evidence, understanding device coverage, and turning tester feedback into something you can act on.
Recruitment without coordination.
Finding people is one step. Keeping the test organized, following up on check-ins, and collecting usable evidence is another.
Installs are not the same as testing.
A tester list does not tell you whether participants used the app, reported issues, or stayed engaged throughout the testing period.
Important findings get lost.
Screenshots, device details, steps, expected results, and actual results become much more useful when they are stored in a structured QA workflow.
Managed Android testing, end to end.
The service is designed around the full testing lifecycle — not just the number of email addresses assigned to your project.
Real people, real Android devices
Testers participate through the official Play Store testing flow using real Android devices.
Daily engagement tracking
Project activity can be reviewed through daily check-ins rather than relying on a single final count.
Screenshots and issue reports
Tester-submitted screenshots, written feedback, and bug reports can become part of the project's evidence.
Device matching
Projects can request device coverage and match the requirements against the tester network.
QA findings
Tester observations can be organized into bugs, UX findings, crashes, severity, expected behaviour, and actual behaviour.
Final testing report
The completed project can be summarized with engagement, device coverage, findings, and recommendations.
From opt-in link to documented testing evidence.
You keep control of your Play Console. ClosedTest manages the testing operation and gives you a record of what happened.
Send the testing setup
Provide the closed-testing opt-in link, app name, and any specific test scenarios or device requirements.
Match and assign testers
Testers are assigned according to the project requirements, with device and Android coverage available when recorded.
Track the testing window
Daily check-ins, screenshots, feedback, and reported issues build the evidence while the project is running.
Review QA and final results
Review structured findings, device coverage, engagement, and the final testing report before you complete your production access process.
Understand the requirement before you start.
ClosedTest publishes free tools and guides so developers can understand their testing position before purchasing a service.
12 Tester Calculator
Calculate tester requirement, safety buffer, testing day, and time remaining.
Free toolProduction Readiness Checker
Review testing, engagement, feedback, and production preparation with a practical checklist.
Definitive guide12 Testers / 14 Days
Read the complete explanation of the closed-testing requirement and production-access process.
TroubleshootingGoogle Play Testing Problems
Troubleshoot tester counts, opt-outs, production access, testing problems, and the questionnaire.
Introductory pricing, all-inclusive.
Google's minimum is 12 opted-in testers. A practical tester buffer can reduce operational risk when participants leave the test.
Not sure yet? See what the final report looks like in a sample report (example data). Then check the real testing outcomes and live testing results before you decide — no invented numbers, just the actual record.
Best for: your first closed test, meeting Google's exact requirement.
- 12 testers · 14-day closed test
- Testers open your app daily and send a screenshot
- Testing based on your submitted instructions
- Live testing dashboard access
- Day-14 final report with findings & recommendations
- Free tester replacement
Best for: most projects — a safety margin against tester drop-outs.
- Everything in Minimum
- 16 testers · 14-day closed test
- 4-tester buffer above the minimum
- 2 Pro testers writing detailed notes
- Priority start (usually < 12h)
Best for: commercial apps, or a second attempt after a prior rejection.
- Everything in Safe Buffer
- 20 testers · 14-day closed test
- 8-tester buffer above the minimum
- 4 Pro testers writing detailed notes
- Extended final report with prioritized fix recommendations
You can provide your testing instructions during setup. The plan price covers the tester count and 14-day testing period shown above. Extensive feature-by-feature testing or unusually labor-intensive QA work may require additional charges. Your app also needs an English language option, so our testers can navigate it. Without one we cannot start the test, and we refund you in full.
Save with a multi-app discount.
Developers with multiple apps can save on every plan above.
Discount applies across any combination of plans — mix Minimum, Safe Buffer, or Maximum as needed for each app.
Tell us how many apps you have and we'll send you a personal link with your discount already applied.
Have multiple apps? Contact us for your promo code →We publish real numbers, not giant marketing claims.
The network and testing metrics above are calculated from our database. We do not publish tester names, customer identities, private project details, or unsupported success claims.
See the public testing results or success stories as the verified testing record grows.
— The ClosedTest team · founded 2026
Real people. Ask us anything before you pay.
ClosedTest coordinates a growing network of Android testers and manages the testing operation directly. When you contact us, you are talking to the team responsible for your testing run.
Targeted Android testing instead of a generic tester list.
The network records tester device and Android-version information so projects can be matched to the coverage they actually need.
- Real Android device coverage
- Android-version coverage
- Country-based tester inventory
- Project-specific device matching
- Tester replacement when needed
Get paid to test Android apps.
We are growing the tester network. If you have a real Android phone, a genuine Google account, and can complete daily testing tasks, you can apply to join.
- Join through official Play Store testing links
- Open assigned apps and record findings
- Submit check-ins, feedback, and screenshots
- Get paid for completed testing cycles
Straight answers about Android closed testing.
Is it 12 or 20 testers?
What do testers actually do during the test?
Do you track daily testing?
Do I receive screenshots and bug reports?
Do you track devices and Android versions?
Can testers be replaced?
Do I need to give you Play Console access?
Can you guarantee Google will approve my app?
Does my app need an English language option?
What do I receive at the end?
Have a question before you start?
Ready to start? Pick a plan above — after payment you'll fill in your app details and we take it from there. For anything else — questions, custom requests, or help along the way — reach us here.