Hire Testers for Google Play: What to Check First

Hiring testers for Google Play is a purchase with an unusual specification: you are not buying twelve installs, you are buying a continuous state that has to hold for 14 days. Google requires at least 12 testers opted in continuously for the 14 days preceding your application, so the second week is the part of the product that matters.

That reframes what you should be buying. A seat count is easy to sell and easy to deliver — twelve email addresses, twelve installs. Continuity is harder, costs more to operate, and is the only thing that protects your 14-day window from an opt-out on day 9. In our own campaigns, the failures we see are overwhelmingly continuity failures, not recruitment failures.

Six questions will tell you which kind of service you are looking at.

1. What happens when a tester drops out?

The most important question, and the one most vendors answer vaguely.

The answer to check against is the honest one: people drop out, and the service absorbs it. OnTesters replaces testers who drop out and includes free retesting, which is the part of our product that addresses the actual failure mode.

2. Are these real devices or emulators?

This is where cheap gigs fail. Emulator instances and duplicate accounts can inflate an install count and cannot produce a genuine closed test. Google's review considers whether testing was real, and community product experts have been explicit that emulators do not count as legitimate closed testers.

Ask directly, and ask for specifics rather than a yes: which device models, how many unique devices across the cohort, and whether testers are verified Android users with their own Google accounts. OnTesters runs testers on real devices across an average of 8-9 unique device models per campaign — device diversity is also a Google best practice, because it surfaces bugs that a single emulator never will.

3. How can I verify opt-ins myself?

You should be able to. The opted-in count lives in Play Console, and it is your number to check — not something you should take on trust from a vendor's screenshot.

A competent service will welcome the question. You should expect to be able to log into Play Console daily and see the count hold. If a vendor is cagey about what you will be able to observe, that is the answer.

4. What exactly is included?

Headcount is the smallest part of the specification. Compare on these axes instead.

Pricing structures differ — OnTesters starts at $14.99 for 12 testers over 14 days — but price comparison is meaningless before you have established what is in the package. Ten seats with no replacements is a different product from ten seats with replacements, even at the same number.

5. What is the vendor promising about the outcome?

Google states that meeting the testing criteria lets you apply for production access, and that review usually takes seven days or less. Nothing in the policy says anything about a service being able to influence that review.

So here is the line to draw:

• Fine: "We provide 12 verified testers who stay opted in, and we replace anyone who drops out."
• Fine: "We include free retesting if you need to run the window again."
• A red flag: "We guarantee production access."
• A red flag: "Guaranteed approval, or your money back" — presented as an approval guarantee rather than a refund policy.

No vendor can guarantee an outcome Google decides. A guarantee is either marketing you should discount, or a signal that the vendor does not understand the process it sells into. OnTesters' position is the same as it has been under our previous TesterBee branding: we sell testers and continuity, not approval.

6. What are the refund terms, literally?

Read them. A refund policy that covers "we did not deliver the testers" is different from one that covers "your application was rejected because engagement was poor."

Ask in writing: what exactly triggers a refund, what evidence is required, and how long the process takes. Then check it against the published policy rather than a sales message.

Red flags worth walking away from

• Prices that imply unbounded replacement at a fraction of market cost.
• Any suggestion that you should not check Play Console yourself.
• Encouragement to use emulators or "multiple accounts" to pad the count.
• Claims about approval rates or guaranteed outcomes.
• A vendor who does not know the current number is 12, not 20. If their playbook predates December 2024, ask what else it predates.
• No explanation of what their testers actually do during the 14 days.

Before you pay, in one list

1. Ask what happens on a dropout, and how fast the replacement arrives.
2. Ask for device specifics, not a yes/no on real devices.
3. Confirm you can verify opt-ins in Play Console daily.
4. Get the inclusions list in writing: replacements, retesting, feedback, buffer seats.
5. Read the refund policy itself, not the sales message.
6. Discount any language that promises approval.
7. Check the vendor knows the current rule is 12 testers and 14 continuous days.

How tester services price continuity

Once you are comparing quotes, the numbers stop being comparable, because different vendors are selling different things and the price reflects which.

OnTesters prices at $14.99 for 12 testers over 14 days, with replacements for dropouts and free retesting included. Read that against the table rather than against another vendor's headline: a cheaper per-seat quote with no replacement mechanism is a different product, and the difference shows up on day 8, not on the invoice. What to check before paying is set out in Google Play Closed Testing Service: Buyer Checklist.

Questions to ask a service before you buy

1. If a tester opts out on day 8, what happens, who pays, and how fast does the replacement opt in? The single most important question, and the one most vendors answer vaguely.
2. Which device models will the testers use? "Real devices" is a claim. A list of models is a specification. OnTesters averages 8-9 unique device models per campaign.
3. How many testers do you recommend? A vendor who says 12 is selling the floor. One who says 15-16 because the requirement is continuous understands the problem. One who says 20 has not updated their playbook since December 2024.
4. Can I verify the opted-in count myself? You should be able to, daily, in Play Console. Reluctance to let you check is the answer.
5. What feedback do I get, and in what format? You must summarise testing feedback when you apply for production access.
6. What is your refund policy, literally? Read the published terms rather than the sales message.

The pattern behind a good answer is that it describes what the provider does when something goes wrong. A good answer describes the component, not the outcome. Anyone promising the outcome is selling something Google decides — see Play Console Production Access: Eligibility vs Approval.

What a good vendor relationship looks like after purchase

The purchase is the start of a two-week relationship, and how it is conducted tells you whether the provider is genuinely managing continuity or simply delivered a list.

• You are given replacements without asking, or told on the day a tester leaves rather than when you notice the count dropped.
• You can see the opted-in count yourself in Play Console, daily, without needing a status update from anyone.
• Device information arrives with the testers, not as an answer to a follow-up question. OnTesters averages 8-9 unique device models per campaign.
• Feedback is collected in a channel you can read, and it is tied to app versions so you can connect a report to the build that caused it.
• Nobody promises the approval. A provider that understands the process describes the component it supplies, not the outcome Google decides.

The single clearest signal is the one you experience on day 8, when a tester leaves and nobody tells you. If you discover that yourself in Play Console and have to initiate the replacement, you bought seats. If it is handled before you notice, you bought continuity, and that difference is what the price gap between the two models actually represents.

What to agree in writing before you pay

Everything in this article is easier to enforce if it is settled before money changes hands. Four lines in a message is enough.

• Number of testers and the window length, stated as "at least 12 opted in continuously for 14 days."
• What happens on a dropout: who replaces them and how quickly.
• Whether retesting is included if Google asks for more testing.
• What feedback you receive, in what format, and when.

None of that is adversarial. It is the same list a competent provider will already have published, and asking is a cheap way to find out whether it exists. What to do with the answers is set out in Google Play Closed Testing Service: Buyer Checklist.

The one number to watch after you buy

If you take a single habit away from this article, make it this: check the opted-in count in Play Console every day of the window, whether you recruited the testers yourself or paid someone to.

It takes ninety seconds. It is the number Google measures, it is the only count that appears in front of a reviewer, and it is the difference between finding a dropout on the day it happens and finding it on day 13. No provider can substitute for it, because you are the only person with a genuine stake in the outcome.

Frequently Asked Questions

Is it allowed to pay people to test my app?

Yes. Google does not prohibit paying testers. What matters is that they are real users on real devices who satisfy the continuous 14-day opt-in requirement, and that the testing is genuine rather than simulated.

How much should hiring testers cost?

Pricing varies by what is included. Compare on replacements, retesting, feedback, and buffer seats rather than on headcount. OnTesters starts at $14.99 for 12 testers over 14 days with replacements and free retesting included.

Can a service guarantee I will be approved?

No. Meeting the 12-tester, 14-day requirement makes you eligible to apply, and Google reviews each application. Any vendor offering a guaranteed approval is describing something outside the policy.

Do the testers need to be in my country?

No. There is no geographic restriction on closed testers. OnTesters has worked with developers across 80+ countries, and the requirement is the same worldwide.

What if Google asks for more testing after I apply?

Google documents that as a possible outcome, citing fewer than 12 opted-in testers and insufficient engagement as reasons. Free retesting in your package is what determines whether that costs you money as well as time.

Sources

Google Play Console Help — App testing requirements for new personal developer accounts (requirement, review timing, continued testing reasons, feedback summary obligation). Google Play Console Help — Set up an open, closed, or internal test. Google Play Developer Community — closed testing metrics thread on emulators (community content, not policy text). OnTesters service details and campaign figures are our own.