A good closed testing service gives you real people on real Android devices who opt in to your closed test and use your app for the full 14 continuous days, and it is open about how that works. A bad one promises things nobody can promise, such as guaranteed approval, or offers things that break Google Play policy, such as reviews or installs. The questions below help you tell them apart before you pay.
This is a checklist, not a ranking. It applies to any provider, including us.
First, know what a service can and can't do
The requirement for personal accounts created after November 13, 2023 is a closed test with at least 12 testers opted in continuously for 14 days when you apply for production access. If you're new to the rule, start with what Google Play closed testing is.
A service can supply testers and keep them active. It can't:
- decide your production access. Google makes that decision, and it may ask for more testing for "insufficient tester engagement."
- shorten the 14 days. The period is set by Google.
- make your app policy-ready. Crashes, a missing privacy policy or broken login credentials are yours to fix. See the common reasons production access is denied.
Also worth knowing: Google's official documentation doesn't mention paid testing services at all. A community guide written by Product Experts says reaching out to third-party testing companies "does not violate the policy," but that is their view, not a Google policy statement. Be wary of any provider that claims Google approves, endorses or partners with it.
Questions about the testers
1. Are the testers real people?
Ask directly. Testers should be individual people with their own Google accounts, not emulators, bots or freshly created throwaway accounts. Automated or fake accounts go against the idea of real users trying your app and risk running into Play policy on manipulation.
2. Do they use real Android devices?
Real phones show real-world crashes, screen sizes and Android versions. Ask what kind of devices are used, in general terms.
3. How many testers, and is there a buffer?
Twelve is the minimum on the day you apply. A provider that offers exactly 12 leaves no room for a single dropout. Ask what happens if a tester leaves: a dropout before day 14 can put you under the minimum.
4. Where are the testers based?
This matters for setup. Your closed track only reaches testers in the countries and regions you've selected, so you need to include the provider's country. Ask which country to add before you start.
5. How do they join your test?
Most services use either a Google Group you add to your track or a list of email addresses. Either works; ask which one, and check it against how testers join a closed test.
Questions about the process
6. What will they actually do for 14 days?
"Opt in and keep it installed" is the minimum. Ask whether testers open and use the app during the period, and whether they send feedback you can summarize in your application. Engagement is one of the two reasons Google gives for asking for more testing.
7. When does testing start, and how is the start confirmed?
Ask how they schedule new orders and how you'll know testers have opted in. You can always verify the count yourself in Play Console.
8. Can you follow progress?
Look for some form of tracking: a status page, regular updates or a clear point of contact. You shouldn't have to guess whether day 9 happened.
9. Do they help with setup?
Most delays happen before day one: a missing country, a change that was saved but never sent for review, a link that isn't live yet. A provider that walks you through the Play Console steps saves you days. Why tester invites aren't approved explains the most common one.
Questions about honesty and terms
10. What exactly do they promise?
The safest promise is about what the provider controls: real testers, the duration, their own process. Treat "guaranteed approval" or "guaranteed production access" as a red flag, because no one outside Google can guarantee it.
11. What happens if something goes wrong?
Read the refund or guarantee terms before paying. What's covered, what you need to do to qualify, and by when?
12. Are price and payment clear?
The full price, the currency and what's included should be visible before checkout.
Red flags: walk away
- Offers of ratings, reviews or installs. Google Play policy prohibits "inflating product ratings, reviews, or install counts by illegitimate means, such as fraudulent or incentivized reviews and ratings" (User Ratings, Reviews, and Installs). Testers also can't leave public reviews on test versions. A service offering this is putting your account at risk.
- Guaranteed approval or a fixed approval date.
- Promises to skip or shorten the 14 days, or claims that fewer than 12 testers is enough.
- Bots, emulators or "accounts" sold in bulk.
- Claims of a Google partnership or official status.
- Selling access to a group for a fee without any testing process. The community guide warns these "are not recognized testing companies."
Quick buyer's checklist
- Real people with their own Google accounts
- Real Android devices
- More than 12 testers, or a clear plan for dropouts
- Clear instructions: which group or emails, which country
- Testers actually use the app and give feedback
- A way to follow progress
- No approval guarantees, no reviews, no installs
- Clear price and refund terms
Doing it yourself is also an option
Google's own advice is to recruit friends, family, colleagues, classmates and communities where your future users are. If you can gather 12 or more engaged people, you don't need a service at all. For a side-by-side look at the free routes and what a service actually costs you in money and time, see how much closed testing costs.
If you'd rather use one, GoPlayTester is one option: 12+ real testers in Indonesia on real devices for 14 continuous days, a published setup guide, daily progress tracking, and no promise of approval because Google decides. Whichever provider you choose, ask these questions first.
