Side-by-side
| Closed Testing | Open Testing | |
|---|---|---|
| Required before production | ✅ Yes (for new apps since 2023) | ❌ No |
| Min testers | 12 | 0 |
| Min duration | 14 consecutive days | none |
| Visibility | Invite-only (testing URL) | Public on Play Store with "Early access" badge |
| Best for | Stability + Google fraud check | Wider feedback before full launch |
| Verifiable report | Yes — TestHive generates one | No |
When to use Closed Testing
Always, if your app is new. Google Play introduced the 12 × 14 Closed Testing requirement for all new apps in late 2023. Without it, you can't promote your app to the production track.
Closed Testing is also the right call when:
- You want focused feedback from people you can communicate with directly
- Your app has critical bugs you don't want public exposure of yet
- You want a verifiable testing record (TestHive issues a SHA-256 verifiable PDF report)
When to use Open Testing
After Closed Testing is done, and you want a wider beta pool before full launch. Open Testing:
- Lets anyone with the link join
- Shows up on Play Store with an "Early access" badge
- Useful for soft-launch testing — production-like exposure with the ability to pull back
But Open Testing doesn't replace Closed Testing. Google's requirement is specifically about the Closed track.
Typical launch sequence
A common indie launch playbook:
- Internal Testing (few days) — your own devices, sanity check the build
- Closed Testing (14 days minimum) — 12 testers via TestHive, gather structured feedback, generate verifiable report ⭐
- Open Testing (1-2 weeks, optional) — soft launch with 50-500 users for last-mile bugs
- Production — promote to public Play Store
Steps 1 and 4 are obvious; the interesting choice is between steps 2 and 3.
Cost comparison
| Track | Tester recruitment cost | Time cost | TestHive cost |
|---|---|---|---|
| Closed Testing | $0-$50 via TestHive | 14 days mandatory | Free (Karma) or $10+ (T-Coin) |
| Open Testing | $0 (you self-recruit) | 0 minimum, optional | N/A (TestHive doesn't broker Open) |
For most indies the cost difference is negligible — the time cost of finding tester volunteers for Open Testing usually exceeds the few dollars you'd spend on TestHive for Closed.
Where TestHive fits
TestHive only handles Closed Testing. We don't broker Open Testing because:
- Open Testing's incentive structure is fundamentally different (volunteers, not paid)
- Google's fraud check doesn't apply to Open the same way it does to Closed
- We want to be deeply specialized in the Closed Testing pain point — 12 × 14 reliability
If you need Open Testing testers, the typical channels are: your Twitter/X audience, your subreddit, your Discord. TestHive's job is getting you through Closed Testing cleanly so you can reach Open Testing in the first place.