The short answer: at least 14 days
Google Play Closed Testing takes a minimum of 14 consecutive days. This is the part of the timeline you cannot shorten — 12 unique testers must each be active every day for 14 days in a row.
The full timeline, phase by phase
| Phase | Typical time | Can you speed it up? |
|---|---|---|
| Recruit 12 testers | Hours (marketplace) to weeks (manual) | Yes — use a tester marketplace |
| The 14-day window | Exactly 14 consecutive days | No — fixed by Google |
| Apply for production access | Minutes to fill out | — |
| Google production review | A few days (varies) | No |
| End-to-end | ~15-20 days | Only the recruitment phase |
Why the 14 days can't be compressed
Google measures continuous daily engagement, not total activity. Twenty-four testers for seven days does not substitute for twelve testers across fourteen days. The window is designed to capture two full weekly usage cycles, which is what their anti-fraud model checks for.
What actually slows people down
It's almost never the 14 days — it's everything around them:
- Slow recruitment: finding 12 reliable testers can take weeks if you do it by hand.
- Resets from drop-outs: if a tester goes quiet mid-window, the 14-day clock can restart, doubling your timeline.
How TestHive keeps you on the 14-day floor
TestHive fills all 12 tester slots within hours, tracks daily activity, and auto-replaces drop-outs within 24 hours so your 14-day window never resets. That keeps your real-world timeline as close to the 14-day minimum as Google allows.