How We Test Your App
We test your app with real people on their own Android devices and Google accounts. After you share your closed testing opt-in link, 12 or more testers opt in, install your app from Google Play and use it every day for 14 continuous days. They report bugs, crashes and UX notes with screenshots, and you get a day-14 report.
Real people, real devices, daily use for 14 continuous days, and a report at the end. Here is exactly what happens during your closed test.
This page explains exactly what happens during your closed test, from the moment you send us your opt-in link to the report you receive on day 14. Google's app testing requirements for new personal developer accounts ask for a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. Our job is to make that test real: real people, using your app every day.
Real people on real devices
Every tester is a real person using their own Android device and their own Google account. We do not use emulators, we do not use bots, and testers do not post fake reviews. When a tester opens your app, it is a real phone in someone's hand, running the build you published to your closed testing track.
Step 1: You share your opt-in link
Send us your closed testing opt-in link and your app's package name. We send back the tester list, which you add to your closed test in Play Console. That is the only setup work on your side.
Step 2: Testers opt in and install
Once the list is added, our testers join your closed test through your opt-in link and install the app from Google Play on their own devices. From then on, your test has the testers it needs, and none of them are you or another developer waiting for a favour in return.
Step 3: Daily opens and use for 14 days
Testers open your app and use it every day. That means actually moving through it the way a normal user would, not launching it and closing it again. Daily use is what keeps your test active for 14 continuous days, which is the part of the requirement that free tester exchanges most often break when volunteers drop out mid-test. Our guide to what 12 testers for 14 continuous days means explains the rule in detail.
What the feedback includes
While they use your app, testers note what they run into. Feedback covers:
- Bugs: things that do not work the way they should.
- Crashes: where the app closed or froze, and what the tester was doing at the time.
- UX notes: screens that were confusing, unclear labels, and layouts that felt awkward on their device.
- Screenshots: so you can see exactly what the tester saw.
What the day-14 report includes
On day 14 you receive a report that brings the whole test together in one place:
- Tester count: how many testers took part in your closed test.
- Engagement summary: how testers used your app across the 14 days.
- Feedback summary: the bugs, crashes and UX notes, with screenshots.
How the report helps your application
When you apply for production access, Google asks about your closed test. Our production access checklist lists what to prepare before you apply. The day-14 report helps you answer from what actually happened during the test, and the feedback gives you real issues to fix before launch. Google makes the final decision on production access. No tester service controls it, and we do not claim to.
Frequently asked questions
How do I get 12 testers for Google Play closed testing?
Send us your closed testing opt-in link and package name. We send back the tester list to add in Play Console, and our testers opt in and install your app on their own devices. Basic gives you 12 testers and Pro gives you 20.
Do testers need to stay opted in for 14 days?
Yes. Google requires at least 12 testers opted in continuously for the preceding 14 days when you apply for production access. Testers who opt in, test for fewer than 14 days and then opt out do not count.
Are the testers real people on real devices?
Yes. Every tester is a real person using their own Android device and Google account. No emulators, no bots, no fake reviews.
What does the feedback include?
Bugs, crashes, UX notes such as confusing screens, unclear labels or awkward layouts, and screenshots showing what the tester saw.
What is in the day-14 report?
The tester count, an engagement summary showing how testers used your app across the 14 days, and a feedback summary with the bugs, crashes and UX notes, with screenshots.
What happens if Google rejects production access?
Google makes the decision on production access. If Google declines because the testing requirement wasn't met, you choose a full refund or a free re-test.
Google's rule: App testing requirements for new personal developer accounts (Play Console Help).
Ready to start your 14 days?
Send your opt-in link today and we'll get your test started.