Short answer: a good closed testing service supplies real people who opt in, install from Google Play, use your app for the whole 14 days and send feedback you can summarise. Be cautious of anyone promising guaranteed approval, selling reviews or ratings, or using accounts that never open your app. Ask these nine questions before you pay.
Why people use services at all
Google's own advice is to recruit from your network and communities. That works for many developers, but solo founders and developers outside large networks often struggle to keep 12 people active for two weeks. A service fills the gap, as long as the testing is genuine.
The nine questions
1. Are testers real people on their own devices?
Ask what devices and Android versions they use.
2. How many testers do I get, and is there a buffer?
If one drops out, do you still have 12?
3. How do testers opt in?
They must use your opt-in link and install from Google Play.
4. What do testers do each day?
Look for daily tasks, not just installs.
5. What evidence do I receive?
Bug reports with steps to reproduce, screenshots and a final report.
6. Can I see a sample report?
A service confident in its work shows one. TestLancer publishes a sample report.
7. Do you sell reviews or ratings?
The right answer is no.
8. Do you guarantee approval?
The right answer is also no. Only Google decides.
9. What happens if Google asks for more testing?
Ask whether you can extend and on what terms.
Red flags
Guaranteed approval, "instant" testers with no device details, bundles that include reviews or installs, and testers who ask you for your Play Console login. You never need to share your Play Console credentials for someone to test your app.
How TestLancer approaches it
TestLancer offers closed testing packages with 12 or more testers, daily tasks, evidence and a report you can use when applying for production access. It doesn't sell reviews, ratings or installs, and it can't guarantee approval.
The official rules, in one place
According to Google's Play Console Help article on app testing requirements for new personal developer accounts:
- The rule applies to personal developer accounts created after November 13, 2023.
- You must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days.
- Production and Pre-registration stay disabled until you meet the requirement; you then apply for production access from the Dashboard.
- The application has three parts: About your closed test, About your app/game and About your production readiness.
- Review usually takes seven days or less, but can take longer. If engagement was too low or you had fewer than 12 opted-in testers, Google may ask you to keep testing.
- Testers who opt out before 14 days don't count, and if someone opts out and back in, their 14 days must be consecutive.
Quick checklist before you apply for production access
- [ ] At least 12 testers opted in today, each for 14 or more days in a row (check your log, not your memory).
- [ ] A buffer of extra testers in case someone drops out at the last minute.
- [ ] Notes on which features testers used, and whether that matched how you expect real users to behave.
- [ ] A short summary of the feedback you received and how you collected it (Play testing feedback, a form, a chat group).
- [ ] A list of changes you made because of the test, with version numbers.
- [ ] Working test credentials in Play Console if your app needs a login.
- [ ] Content rating, target audience and data safety answers that match the real app.
- [ ] No crashes or empty screens on the build you're about to ship.
If any box is empty, a few more days of testing usually costs less than another review cycle.
Mistakes that cost developers extra weeks
- Recruiting exactly 12. One opt-out and you're back to waiting.
- Running the test on the internal track. Internal days don't count toward the requirement.
- Sharing an APK instead of the opt-in link. Testers must opt in and install from Google Play.
- Tidying the tester list mid-test. Removing someone ends their streak.
- Shipping no updates. The production readiness section asks what you changed because of testing.
- Using friends who never open the app. Google can ask for more testing when engagement is low.
- Buying reviews or ratings. They break Google Play policy and give you nothing to report. TestLancer never sells them.
FAQ
Is paying for testers against Google policy?
Google's article focuses on genuine testing and engagement. Avoid anything that fakes engagement or sells reviews.
How long does a service take?
At least the 14 days Google requires, plus setup time.
Can a service fix my app's bugs?
Testing finds them; you or your developer fix them. Some providers, TestLancer included, also offer app development.
Next step
If you can't find 12 reliable people on your own, TestLancer's Google Play closed testing service runs a 14-day closed test with real testers who opt in, use your app and send feedback you can summarise in your production access application. You can also use the free Google Play Launch Center checklist first. TestLancer does not sell reviews, ratings or installs, and no one can guarantee Google will approve production access. Your app still has to meet Google Play policy.
Top comments (0)