12 testers, 14 consecutive days, handled end to end
This is the deliverable the policy asks for and nothing more: a group that meets the minimum every day of the window, on real hardware, with the engagement record you will need when you apply for production access. One flat fee. No subscription.
You are buying
- 12 verified testers, opted in. Unique Google accounts, personal physical Android devices, real installs through your own opt-in link. No emulators, no device farms, no scripts.
- A 2-3 tester buffer above the minimum. You are buying 12 counted testers and receiving 14 or 15. The extra names exist so the count never dips below the policy floor.
- Free replacement for dropouts. If a tester goes quiet, uninstalls, or opts out, we assign a replacement at no extra charge — including deep into the window.
- Daily engagement monitoring for 14 days. Session activity is tracked day by day. You see who opened the app and when, rather than discovering a flat line on day 12.
You are not buying
- A guaranteed approval. Google decides, not us.
- Access to your Play Console account, build, or signing key.
What is inside the 14-day cycle?
Six commitments, each of which exists because its absence caused a failed window for somebody.
12 verified testers, opted in
Unique Google accounts, personal physical Android devices, real installs through your own opt-in link. No emulators, no device farms, no scripts.
A 2-3 tester buffer above the minimum
You are buying 12 counted testers and receiving 14 or 15. The extra names exist so the count never dips below the policy floor.
Free replacement for dropouts
If a tester goes quiet, uninstalls, or opts out, we assign a replacement at no extra charge — including deep into the window.
Daily engagement monitoring for 14 days
Session activity is tracked day by day. You see who opened the app and when, rather than discovering a flat line on day 12.
Bug reports you can act on
Findings arrive with device model, Android version, and reproduction steps, so a fix does not start with an investigation.
Questionnaire support at the end
When the window closes, we hand you the tester feedback and bug history that the production access questionnaire asks you to describe.
How the 14 days actually run
The window is easy to describe and easy to get wrong. Here is the sequence, including the boring steps that hold everything else up.
- 01
Before day 1
Your closed track goes live
You create the closed testing release, Google reviews it, and the track status changes from In review to Active. Testers clicking an opt-in link on a pending track see an error page, so this step has to finish first.
- 02
Within 24 hours
12 testers install and open the app
We match testers to your opt-in link. Most campaigns see the first installs inside 6 to 12 hours and the full group inside 24. This is when your 14-day countdown effectively begins.
- 03
Day 1 to 13
Daily sessions, your fixes ship as they land
Testers open the app on repeated days and work through your core flows. When you push a build to the same track, testers update to it without re-opting in — which is why shipping fixes mid-window is safe and worth doing.
- 04
Day 14
The window closes with the data intact
You finish 14 consecutive days with a group that never fell below the minimum and a log of what testers reported. From here the remaining work is the production access application.
- 05
After day 14
Apply for production access
The questionnaire asks how you recruited testers, what feedback you received, and what you changed. Your campaign dashboard holds the material for all three answers.
Why 12 is a number, not a plan
Twelve is the floor. It is also the most fragile possible group size, because it leaves no room for the ordinary things people do. Here is what we observe across a two-week window.
| Starting group | Active by day 10 | Status | Why |
|---|---|---|---|
| Exactly 12 | 9 to 11 by day 10 | High risk | One uninstall, one phone swap, or one tester who opts out drops you below the floor with no way to recover except finding a replacement yourself. |
| 14 (our standard) | 12 to 13 by day 10 | Safe | Absorbs two dropouts without touching the minimum. This is the tier we ship by default at the 12-tester price. |
| 15 to 20 | 13 to 17 by day 10 | Extra headroom | Useful when your app has a narrow feature set, is in a non-English language, or you want broader device coverage per cycle. |
The dropouts are rarely dramatic. A tester changes phones. Someone travels and stops opening the app. A person decides the amount of effort does not match the reward and opts out. None of those are failures of the tester; they are the normal attrition of a two-week commitment. The mistake is planning a two-week commitment around exactly the minimum number of people. More on the causes in our write-up on opt-outs and resets.
What if your app is not a simple one?
Most cycles are straightforward: an app bundle on a closed track and a link to hand over. Five situations need something extra, and all five are settled at setup rather than discovered on day three.
Paid apps and in-app purchases
Generate 100% discount promo codes in Play Console under Monetize, then paste them into campaign setup. Testers redeem a single-use code so they reach the paid screens without paying. Without codes, testers hit a paywall and your premium flows go untested for the whole window.
Sign-in gated builds
Supply two or three test accounts with pre-seeded data. A tester who cannot get past the sign-in screen produces fourteen days of activity that never touches the feature you wanted tested. If sign-up is self-serve, say so and testers will register properly instead.
Non-English interfaces
We run testers in non-English locales and use our on-screen overlay translator when the interface language differs from the tester's. Findings still come back written in English, so there is no translation step on your side.
Features that need two devices
Pairing flows, calls, and anything multiplayer need testers coordinating with each other. Tell us at setup and we arrange the pairings. Left unarranged, every test case that needs a second device is unreachable.
Feature flags and hidden menus
If a flow only appears behind a debug menu, a staging configuration, or a flag, tell us how to reach it. A tester who never finds the entry point tests the public build and nothing else.
Who should not book this?
Three groups of developers land on this page and do not need what we sell. Saying so is cheaper than selling you a cycle you could have skipped.
Organization accounts
If your Play Console account is verified as an organization with a D-U-N-S number, the closed testing requirement does not apply to you. You can apply for production access directly.
Accounts that predate the policy
Personal accounts created before 13 November 2023 are outside the requirement, as are accounts with an app already approved and live in production.
iOS or cross-platform test management
We test Android builds. If you need TestFlight coverage, that is a different tool and we are not the right answer for it.
Unsure which group you are in? The personal versus organization account comparison walks through the distinction.
$14.99
One-time fee for the complete cycle: 12 counted testers, the buffer above the minimum, and free replacement. The tiers for 15, 20, and 25 testers exist for broader device coverage rather than to unlock anything.
See all plansRefund if production access is refused for tester engagement
Booking and logistics
What developers ask before they hand over an opt-in link.
How much does a 12-tester, 14-day cycle cost?
From $14.99 per app as a one-time fee. There is no subscription and no charge for replacing a tester who drops out. Higher tiers for 15, 20 and 25 testers exist for wider device coverage rather than to unlock anything.
How quickly does the 14-day window start?
The countdown effectively begins once the group is installed and opening the app. Most campaigns see the first installs within 6 to 12 hours of receiving your opt-in link, with the full group in place inside 24 hours.
Why do you provide more than 12 testers?
Twelve is the policy floor and the most fragile possible group size. A single uninstall, phone swap, or opt-out drops you below the minimum with no margin. A 2-3 tester buffer absorbs that attrition without touching the floor, and replacements are free.
What happens if a tester drops out mid-cycle?
We monitor activity daily and assign a replacement tester at no extra cost, including late in the window. Replacements keep the same device profile where possible so the hardware coverage of your cycle does not degrade.
Do you need access to my Play Console account?
No. We work from the public opt-in link only. We never ask for Play Console credentials, your app bundle, or your signing key.
Who is not eligible for this service?
Organization accounts verified with a D-U-N-S number are exempt from the closed testing requirement. So are personal accounts created before 13 November 2023, and accounts that already have an app approved and live in production. We also test Android only, so TestFlight coverage is out of scope.
Written and maintained by
Afrin Asha
Founder, OnTesters
Android developer and QA specialist. Built OnTesters after working through Google Play’s 12-tester closed testing requirement on real devices.
Platform figures on this page come from campaigns run through OnTesters. Read how the platform works or see the guides library.
Sources
- App testing requirements for new personal developer accounts— the 12 tester / 14 day rule
- Set up an open, closed, or internal test— opt-in links, groups, and update behaviour
Dropout and engagement observations are drawn from 1,500+ campaigns analyzed on our platform. Google publishes the policy; the attrition pattern is ours.
Policy and pricing reviewed September 2026
Start the 14 days this week
Paste your closed testing opt-in link and we take it from there. Most groups are fully opted in within 24 hours.