Setting up closed testing in Google Play Console is straightforward—if you know the exact steps. One wrong click can delay your launch by days. This tutorial walks you through the entire process with screenshots, from creating your first testing track to adding your 12th tester.
By the end, you'll have a live closed testing environment ready for your 14-day testing period. Let's get your app one step closer to production.
Prerequisites: Before You Start
Ensure you have these ready:
- Google Play Developer Account: $25 one-time fee, verified and active
- Signed App Bundle (AAB): Your app signed with your release keystore
- 12 Tester Email Addresses: Gmail or Google Workspace accounts
- App Icon & Screenshots: Required for store listing (even for testing)
- Privacy Policy URL: Required for all apps
Account Type Matters
New personal developer accounts created after November 2024 must complete closed testing with 12 testers for 14 days before accessing production [^20^]. Organization accounts may have different requirements based on verification status.
Step 1: Access the Closed Testing Section
Navigate to Testing
Log into Google Play Console. Select your app from the dashboard. In the left sidebar, click Testing > Closed testing.
Screenshot: Play Console sidebar showing Testing > Closed testing menu
If this is your first time, you'll see an option to "Create track." If you have existing tracks, you'll see them listed here (Alpha, Beta, or custom named tracks).
Step 2: Create Your Testing Track
Create a New Track
Click "Create track" or the blue "+" button. Name your track (e.g., "Closed Testing," "Beta," or "Pre-launch"). Track names are internal-only—testers won't see them.
Screenshot: "Create track" dialog with name input field
Naming Tip
Use descriptive names if you plan multiple testing phases: "Closed-Test-Phase-1," "Closed-Test-Phase-2." This helps track which testers were in which cohort.
Step 3: Upload Your App Bundle
Upload AAB or APK
In your new track, click "Create new release" or "Upload". Drag and drop your signed AAB file (recommended) or APK. Google Play will process it and show version details.
Screenshot: Upload area showing AAB file being processed
Release Details to Configure
- Release name: Internal identifier (e.g., "1.0.0-closed-beta")
- Release notes: What's new in this version (testers see this)
- Rollout percentage: Leave at 100% for closed testing
Step 4: Add Your 12 Testers
Configure Testers
Click the "Testers" tab in your track. Click "Add testers" or the pencil icon. You can add testers via:
- Email list: Paste up to 100 email addresses (comma or line separated)
- Google Groups: Link a Google Group for dynamic management
- CSV upload: Upload a file with email addresses
Screenshot: Testers tab showing email input field and CSV upload option
Critical: Tester Requirements
All 12 testers must have Google accounts (Gmail or Google Workspace). They must opt-in to testing and remain active for 14 consecutive days. You cannot have fewer than 12 at any point during the testing period.
Email Template for Testers
Send this to your 12 testers before adding them:
Step 5: Configure Track Settings
Advanced Settings
Click the "Settings" or gear icon in your track. Configure:
- Feedback channel: Email address or URL for tester feedback
- Opt-in URL: Direct link for testers to join (share this if they don't get email)
- End testing: Option to end test early (don't use until ready)
Screenshot: Track settings panel showing feedback URL and opt-in link
Step 6: Release to Your Track
Start the Release
Return to the "Releases" tab. Review your release details, then click "Start rollout to [Track Name]". Confirm in the dialog. Your release will show as "In review" briefly, then "Available to testers."
Screenshot: "Start rollout" button with confirmation dialog
Processing Time
Initial releases may take a few hours to process. Subsequent updates are usually instant. Testers will receive email invitations within 24 hours of release.
Step 7: Tester Onboarding Process
Guide Your Testers
Once released, testers must complete these steps:
- Receive email: Subject: "You're a tester for [App Name]"
- Opt-in: Click "Become a tester" button in email
- Access app: Click "Download it on Google Play" link
- Install: App appears in their Play Store as "Early access"
- Test: Use app actively, exploring features
- Feedback: Submit reviews or feedback via your channel
Screenshot: Tester email invitation with "Become a tester" button highlighted
Monitoring Your Testing Period
Track your testing progress in Play Console:
Key Metrics to Watch
- Testers enrolled: Should show 12+ (some may opt out)
- Installs: Track who actually installed
- Ratings: Monitor for feedback
- Crashes & ANRs: Critical stability metrics
Screenshot: Dashboard showing tester metrics and installation stats
Testing Checklist (Days 1-14)
- ☑️ Day 1: Confirm all 12 testers installed app
- ☑️ Day 3: Check for early dropouts, replace if needed
- ☑️ Day 7: Mid-point check, encourage feedback
- ☑️ Day 10: Final push for engagement
- ☑️ Day 14: Testing period complete!
- ☑️ Day 15: Apply for production access
Need Testers? We Handle Everything
Don't struggle to find 12 testers. We provide verified testers, manage the 14-day period, and guarantee approval. You just focus on your app.
Get 12 Testers NowFrequently Asked Questions
To set up closed testing: 1) Log into Play Console, 2) Select your app, 3) Go to Testing > Closed testing, 4) Create track or select existing, 5) Upload your AAB/APK, 6) Add 12 tester email addresses, 7) Save and release to track. Testers receive invitation emails within 24 hours.
Add testers in Play Console under Testing > Closed testing > [Your Track] > Testers tab. You can add individual emails or upload a CSV file. Testers must have Google accounts and will receive email invitations to join the test.
Initial app review for closed testing typically takes a few hours to 24 hours. Subsequent releases to the same track are usually instant. The 14-day testing period starts when testers opt-in and install, not when you release to the track.
Yes, you can add up to 100 testers per track. However, only 12 are required for the production access requirement. Adding more provides a buffer in case some testers drop out or don't engage.
If you drop below 12 active testers at any point, the 14-day period resets. You must maintain 12+ testers continuously for 14 days. Replace dropouts immediately by adding new testers to the same track.
Google Play Console shows "Testing requirements met" in your dashboard after 14 days with sufficient testers. You'll also see a "Apply for production" button appear. This typically happens 24-48 hours after day 14 ends.
Next Steps: After Setup
Once your testing track is live and testers are engaged, monitor the 14-day period closely. After completion, you'll be eligible to apply for production access.
If you encounter issues with the timeline not counting or tester engagement, check our troubleshooting guide.