Can you use your own accounts as testers on Google Play?
Updated
Yes, twelve Google accounts you created will register as twelve opted-in testers. And no, you should not do it.
That is the honest answer, and the reason is not moral. It is that the requirement is not really "twelve accounts" — it is a review you have to pass at the end, and a cohort you built yourself is the thing most likely to fail it, after two weeks you cannot get back. If the real problem is finding twelve people, how to get 12 Google Play testers for free covers the routes that hold up.
What the requirement is actually for
Google introduced closed testing for new personal accounts to filter out low-effort and abusive apps at the point of publication. The test is a cost: convincing twelve people to keep an app installed for a fortnight is meant to be mildly difficult, because that difficulty is the filter.
Understanding that reframes the question. Twelve accounts you own does not satisfy the filter; it routes around it. Production access is granted after a review, not automatically on day fifteen, and the review is where a manufactured cohort has to hold up.
What makes a self-made cohort visible
You do not need to know Google's exact detection to see why this is a weak bet. Twelve accounts created within days of each other, with no prior Play activity, opting into exactly one app, from one or two devices or a set of emulators, on one network, is a distinctive shape. It is distinctive whether or not anyone looks at it manually, and it stays attached to your developer account afterwards.
What is fine
The line is not "people you know are cheating". It is whether the testers are real people with their own Google accounts using their own devices:
- Friends and family. Completely legitimate. A real person with a real account and a real phone is a real tester.
- Colleagues. Same.
- Your own second, genuinely-used account. One account you actually use, on a device you actually use, is a normal tester. Eleven accounts created on Tuesday is not.
- Strangers from a developer community. Real people, real accounts, and they usually give better feedback than your friends because they have no reason to be nice about it.
The distinction is not how you met them. It is whether they exist.
The practical problem this is trying to solve
Nobody considers this because they enjoy account creation. They consider it because they need twelve people, they know four, and the deadline is real.
The realistic answers to that problem:
- People you know. Start here and be specific — a link and an explicit "can you press accept on this" converts far better than a group message. Getting them to genuinely opt in is its own skill; see how to verify a tester actually opted in.
- A test-for-test exchange. Other developers in exactly your position, who understand the ask because they need it too. This is what TestersWiz is — free, reciprocal, and the opt-in is verified against Play Console on both sides, so the testers you get are real accounts that actually count.
- A paid service. A legitimate one supplies real testers and charges for the coordination. Free vs paid app testers sets out when that is the right call.
All three give you a cohort that survives review. The account farm gives you one that has to.
If you have already done it
Do not panic and do not delete anything mid-window — removing testers drops your count and creates exactly the gap the continuous-participation rule cares about. The better move is to dilute: recruit real testers now, get them opted in, and let the genuine share of the cohort grow. A test with twelve real testers and a couple of your own accounts alongside them is a different proposition from one that is twelve accounts you made.
Then, next time, start recruiting on day one rather than on day ten. The two-week clock is the part you cannot compress, and it is the only part.