Internal Testing, Staged Rollout, and Production
Publish first to an internal test track, promote to closed and open testing, then gradually roll out to production using a staged rollout percentage and monitor crash rates.
The Four Release Tracks
Google Play Console offers four release tracks forming a progressive rollout pipeline. Internal testing reaches up to 100 testers instantly with no review. Closed testing (alpha) targets a specific invite list. Open testing (beta) allows anyone to opt in publicly. Production reaches all users in your selected countries. Each track acts as a safety gate — you validate quality at each level before promoting to the next.
// Release track comparison:
// Internal Testing:
// Testers: up to 100 (by email/Google Group)
// Availability: Instant (no Google review)
// Visibility: Hidden from public
// Best for: Team + QA testing
// Closed Testing (Alpha):
// Testers: Specific invite list (no limit)
// Availability: After brief automated check
// Visibility: Hidden from public
// Best for: Beta test with partners/selected users
// Open Testing (Beta):
// Testers: Anyone who opts in
// Availability: Visible public beta badge
// Best for: Community feedback before launchSetting Up Internal Testing
Internal testing is your first stop after a successful build. Create an internal testing release, upload the AAB, and add testers by email or a Google Group. Testers receive an email with an opt-in link — they must click it and then find the app in Play Store to install it. Internal testing builds are delivered within minutes of publishing (unlike production which can take hours for processing). Always verify core flows pass here before promoting.
// Internal testing setup:
// Testing > Internal testing > Testers tab
// > Create email list: 'Core Team'
// > Add emails:
// alice@yourcompany.com
// bob@yourcompany.com
// qa@yourcompany.com
// Share the opt-in link with testers:
// 'Join the test at this link: [opt-in URL]'
// Testers click link, then search for the app on Play Store
// App appears with an 'Internal' badge
// Tester checklist:
// [ ] Sign up flow works
// [ ] Core feature performs correctly
// [ ] No crashes in main pathsAll lessons in this course
- Creating a Keystore and Signing the AAB
- Setting Up the Play Console Listing
- Content Ratings, Policies, and Privacy
- Internal Testing, Staged Rollout, and Production