Requirements
Human testers or automated real devices for Google Play closed testing: what each one gives you
Both can keep 12 testers opted in for 14 days. They differ in what you get for the production access questionnaire: feedback from people, or reliable daily runs with records. How Google reviews your test, the trade-offs of tester panels, swaps, and device-based services, and how to combine them.
Last checked 31. okt 2026.
Google checks two different things
Getting production access on a new personal Google Play account has two steps, and they test different things (Play Console Help):
- Eligibility — at least 12 testers opted in to your closed test for the last 14 days in a row. This is a count, and Play Console shows it on your dashboard.
- The production access questionnaire — how you recruited testers, whether they used your app’s features, what feedback you got and how you collected it, and what you changed because of it. A person reads your answers.
Every way of getting testers is a trade-off between these two. Some are good at keeping the count stable; some are good at producing feedback. Knowing which one you need more is the whole decision.
Three ways to fill the 12 slots
- Human tester panels. A service gives you a list of people (or a Google Group) who opt in and promise to open your app daily. You can get written feedback, sometimes bug reports. You usually can’t see how much each person actually used the app.
- Tester swaps. You test other developers’ apps and they test yours, on Reddit, Discord, or swap apps. Free, but partners drop out, and a single uninstall can push you below 12. See tester swaps.
- Automated runs on real devices. Real Android phones, each signed in with its own tester account, install your app from the Play Store and open it on a schedule. They don’t drop out and every run is logged, but they don’t write feedback.
Side by side
| What you need | Human tester panel | Tester swap | Automated real devices |
|---|---|---|---|
| Keeps 12 opted in for 14 days | Depends on the panel; dropouts are usually replaced | Often breaks — partners uninstall or forget | Yes, devices don't drop out on their own |
| Opens the app every day | Usually promised; hard to verify | Rarely | Yes, at set times, with logs |
| Feedback on your app | Yes, the main reason to choose it | Sometimes, if partners care | No — add a few people of your own |
| Proof of what happened | Varies (reports, screenshots) | None | Run logs, install history, screenshots |
| Cost | Roughly $14–40 per app | Free, costs your time | Similar to tester panels |
The combination that answers both questions
The questionnaire doesn’t ask you to have 12 people who each wrote a review. It asks what feedback you got and what you did with it. So you can split the job:
- Use a service (human or device-based) to keep 12+ testers opted in for 14 days without gaps.
- Add two to five people you know — friends, colleagues, early users — to the same tester list and ask them for honest feedback.
- Ship at least one update during the test that responds to that feedback, and write down what you changed.
- Answer the questionnaire with what actually happened: who tested, how, what they said, what you changed.
Example answers for each question are in How to answer the production access questionnaire, and the most common rejection is explained in ‘Testers were not engaged’.
Red flags, whichever kind you pick
- “Guaranteed approval.” Only Google decides. Look at what happens if you’re rejected — a refund or a free re-run, and under what conditions.
- Ready-made questionnaire answers. Answers describing feedback you never got are the riskiest thing you can submit.
- No way to check progress. You should be able to see whether testers installed your app and kept it for the whole 14 days.
- Paying before anyone can install. If your track’s countries or device compatibility block installs, you want to know before you pay.
Where DUIRE fits
DUIRE is the device-based kind: real Android devices join your closed test, open your app at set times every day for 14 days, pick up new versions, and keep run logs, install history, and per-device screenshots, which we check ourselves. It doesn’t write feedback and doesn’t fill in your questionnaire. Before you pay, our devices check that they can install your app, and if Google rejects your production access request, we run the 14 days again for free if you ask within 30 days of the test ending.
If you’d rather recruit people yourself, start with How to get 12 testers.
Frequently asked questions
- Does Google require the testers to be real people?
- Google's Help Center sets the eligibility rule — at least 12 testers opted in for the last 14 days — and recommends recruiting testers who represent your future users. The production access questionnaire then asks how you recruited testers, whether they used your app's features, and what feedback you got, so answer it truthfully based on what actually happened.
- Can an automated service answer the questionnaire for me?
- It shouldn't. Submitting made-up tester experiences puts your developer account at risk. A device-based service can give you facts — how long the test ran, how many devices installed each version, when updates were picked up — but the feedback part has to come from real feedback you received.
- Is a human tester panel always better?
- Not always. It gives you feedback, but you can rarely verify how much each tester really used the app, and quality varies a lot between providers. If you already have a few people who will genuinely try your app, a device-based service for the headcount plus those people for feedback is often the stronger combination.
- What gets rejected most often?
- Developers most often report "testers were not engaged with your app during your closed test". It points at how testers used the app and what you learned from them, not only at the headcount — see the linked article on that message.
Meet the requirement without recruiting testers
DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.