Closed vs internal vs open testing
| Track | Testers | Visibility | Counts for production? | |-------|---------|------------|-------------------------| | Internal | Up to 100 team | Hidden | No | | Closed | Invited users | Hidden | Yes | | Open | Anyone can join | Public beta | No (different path) |
Use closed testing for the 12/14 requirement.
Setting up closed testing in Play Console
- Play Console → Your app → Testing → Closed testing
- Create a new release → upload AAB
- Add release notes → Review and roll out
- Copy opt-in URL from Testers tab
- Share link with testers (or submit to Fast Testers)
Allow 1–24 hours for Google review of your first closed release.
Managing testers effectively
- Maintain 15+ enrolled to absorb dropout
- Send welcome email with opt-in instructions
- Monitor install count daily
- Push updates only when necessary mid-period
- Never share APK directly — always use Play link
Fast Testers automates recruitment and retention.
Graduating to production
After 14 days with 12+ testers:
- Play Console → Production → Apply for access
- Complete questionnaire
- Wait for approval email
- Create production release from tested build
If denied, read rejection reason, fix, and reapply — testing period remains valid.
Ready to Start Closed Testing?
Ready to Start Closed Testing?
Fast Testers assigns 12 real Android testers in about one hour for a one-time $15 payment. Complete Google's 14-day closed testing requirement and apply for production access with confidence.