Google Play 12 Testers Rule vs the Old 20 Testers
How the requirement went from 20 testers to 12, who it applies to and how many testers you should really recruit.
Read the guide →Is It Safe to Buy Google Play Testers? What to Know
Quick answer Buying Google Play testers can be safe if you get real people on real devices who join your closed test, stay opted in for 14 days and actually use the app. It is risky when the testers are bots, fake accounts or people you must give account access to.
Many developers hit the 12-tester requirement, cannot find enough people and start searching for paid testers. Some services are honest, some are not, and it is hard to tell the difference from a sales page. This guide explains what Google expects, what you are really buying, the red flags, and the questions that separate a safe provider from a risky one. We run a tester service ourselves, so we say so clearly below.
Is it safe to buy Google Play testers?
It can be, depending on what you buy. Paying for real people with real Android devices who join your closed test, stay opted in for 14 days and genuinely try your app is a low-risk way to meet the requirement. Paying for bots, emulators, fake accounts or anyone who needs access to your developer account is risky and can cost you your account.
So the useful question is not “is it safe to buy testers?” but “who exactly are the testers, and what will they do?”. The rest of this guide helps you answer that.
Disclosure: 12AppTesting sells tester packages, so we have an interest here. We have tried to describe the options fairly, including free ones, and we link to Google's own pages so you can check the rules yourself.
What does Google expect from testers?
Google's testing requirements page sets the baseline for personal developer accounts created after November 13, 2023: a closed test with at least 12 testers opted in for at least 14 days in a row, followed by an application for production access. The application asks how you recruited testers, how they used the app and what you changed after their feedback.
| What Google looks for | What that means for a tester | Guide |
|---|---|---|
| At least 12 testers opted in | Each one opens your opt-in link and joins | How to get 12 testers |
| 14 days in a row | They must not opt out part way | 14-day requirement |
| Real use of the app | They open it on different days and try features | Why the button may be missing |
| Honest answers | You can explain how you found them and what changed | Applying for production |
Separately, Google's policy on incentivized actions says developers must not try to manipulate the placement of apps in the store. It defines an action as incentivized if a user is offered money, goods or the equivalent in exchange, and it says incentivized ratings and reviews have always violated its policy. Google advises against incentivized actions in general. That policy is about ratings, reviews and installs, not closed test tester lists, but it shows how Google thinks about bought engagement, so stay on the safe side.
What are you actually buying?
| Option | What it is | Risk | Quality of feedback |
|---|---|---|---|
| Friends and family | People you know join your test | Low | Varies. Often polite rather than useful. |
| Free tester swaps in communities | Developers test each other's apps | Low to medium. Reliability depends on the other person. | Often good, because they are developers |
| Paid service with real people | Real testers on their own devices join your test | Low to medium. Depends on the provider. | Varies. Ask for a report. |
| Bot, emulator or fake-account service | Many accounts controlled by one operator | High | None |
| Anything that needs your account access | Someone logs in to your Play Console | Very high | Not relevant |
The first three are ordinary ways to find testers. The last two are the ones that cause account problems. If a service cannot explain in plain words who its testers are, treat it as the fourth option until proven otherwise. If an account is ever suspended, read what to do if your developer account is terminated.
What are the red flags?
- It asks for your Play Console login or a role in your account. You never need to share this.
- It promises ratings, reviews or installs. That is manipulation, not testing.
- It promises 100% approval with no conditions. Only Google decides, so ask what a guarantee actually covers.
- The price is far below everyone else. Real people cost time. Ask where the testers come from.
- It cannot say how many testers it provides or what happens if some leave. See what to do if testers leave.
- It will not say whether the testers use real devices.
- No contact details, no company name, no way to reach a person.
- It tells you to lie in the questionnaire. Walk away.
What should you ask a provider before you pay?
| Question | A good answer | A worrying answer |
|---|---|---|
| Are the testers real people on physical devices? | Yes, and they install from Google Play | Vague, or “virtual devices” |
| What do you need from me? | My opt-in link, or I upload your tester email list | My Play Console login |
| How many testers do I get, and what if some leave? | A clear number, with replacements or a buffer | No answer |
| Do testers open the app on different days? | Yes, for the whole 14 days | They install it and that is all |
| What does your guarantee cover? | Specific terms, for example extra testing or replacements | “Guaranteed” with no detail |
| Can I contact a real person? | Yes, by WhatsApp or email | Only a form |
| Will you ask my testers to rate the app? | No | Yes |
Should you use paid or free testers?
| Free (friends, communities) | Paid provider | |
|---|---|---|
| Cost | No money, but time | Package price |
| Speed | Slow. You chase people. | Faster. The group is ready. |
| Control | You choose the people | You trust the provider |
| Reliability | People forget or opt out | Usually higher if the provider is good |
| Risk | Low | Low if vetted, high if not |
| Best for | Apps with an audience or helpful friends | Solo developers short on time |
A common pattern is to use both: invite a few friends so you have genuine human feedback, and add a vetted provider so you reach the 12 reliably. The guide on 12 testers vs 20 testers explains how many to aim for.
How do you lower the risk if you buy testers?
- Choose before you payUse the questions above. Prefer a provider you can message directly.
- Share only what is neededSend an opt-in link or upload a tester list. Never share account access.
- Check that testers actually joinedLook at the tester count in Play Console and follow the guide to testers not counting if numbers look wrong.
- Use the feedbackFix bugs, upload a new version, and note what changed. The questionnaire asks for exactly this.
- Skip reviews and ratingsDo not ask testers to rate the app. Let real users do that after launch.
- Answer honestlyExplain how you recruited testers. If something was unclear, say so.
How does 12AppTesting work?
We provide real Android testers on physical devices. You order a package of 12, 15 or 20 testers, we send you our tester email list as a CSV file with a simple guide, you upload it as your list and send us your opt-in link, and our testers handle the rest for 14 days plus 7 extra days. We do not need your Play Console login and we do not ask testers to leave ratings. Packages start at $7.
That is one option among several. If you prefer free testers, the guide on how to get 12 testers shows five ways to find them, and the complete closed testing guide covers the whole route to production.
Part of a series: this article is one chapter of Google Play Closed Testing: The Complete Guide. Start there for the full roadmap from setup to production.
Sources
- Google Play Console Help: app testing requirements for new personal developer accounts
- Android Developers Blog: Google Play's policy on incentivized ratings, reviews and installs
- Google Play Console Help: set up an open, closed or internal test
- Google Play Console Help: developer account termination
Frequently asked questions
Is it against Google Play policy to buy testers?
We did not find a Google statement that forbids paying people to test an app in a closed test. Google does forbid manipulating store placement through fake or incentivized ratings, reviews and installs, and it expects your testers to be real people who use the app. The risk is in what you buy, not in the payment itself.
Can Google tell that testers were paid for?
Google does not publish how it evaluates closed tests. Its production access questionnaire asks how you recruited testers, what they did and what you changed, so answer it honestly.
Should paid testers leave a rating or review?
No. Google defines an action as incentivized if a user is offered money, goods or the equivalent for it, and incentivized ratings and reviews have always violated its policy.
Can a provider guarantee production access?
Only Google decides. Ask exactly what a guarantee covers, for example extra testing days or replacement testers if your application is declined.
Does a provider ever need my Play Console login?
No. A tester provider needs your opt-in link, or you upload their tester email list. Never share your Play Console login.
What is the safest option?
A mix: your own contacts, plus real people from a provider you have vetted, with honest notes about the feedback you gathered and what you changed.
