The Complete Guide to Android Beta Testing: Internal, Closed, and Open Tracks Explained

Google Play Console offers three testing tracks before public release: Internal, Closed, and Open. Understanding the differences — and when to use each — can save you significant time and headaches.

Internal Testing Track

Internal testing is the fastest way to share a build with a small team. You can have up to 100 testers, and the build goes live almost immediately after upload (usually within minutes).

Best for: Early QA with your team. Not suitable for meeting the closed testing requirement.

Closed Testing Track (The One That Matters)

The closed testing track is where you’ll meet Google Play’s publication requirement. Key facts:

• Requires at least 12 unique testers with real Google accounts
• Testers must remain active for at least 14 consecutive days
• Once satisfied, you can apply for production review
• Builds take 24-48 hours to be reviewable by testers

This is the step that trips up most new developers. The solution is simple: use a testing service that provides 12 engaged testers for the full 14-day period.

Open Testing Track

The open testing track is essentially a public beta. Anyone can opt in via the Play Store. This is useful for larger user feedback before launch, but it’s not required.

Best for: Apps that want broader feedback and are already past the closed testing hurdle.

The Path to Production

Stage 1: Build Your App

Complete your app development and prepare a release build (AAB format preferred by Google).

Stage 2: Set Up Play Console

Create your app in Play Console, complete the store listing, set content ratings, and configure pricing.

Stage 3: Internal Testing

Optional but recommended. Test with your immediate team to catch major issues.

Stage 4: Closed Testing (Required)

Upload your build to the closed testing track, invite 12+ testers, and wait 14 days. Use SaaSTest Pro to fulfill this step quickly.

Stage 5: Production Review

Once closed testing is complete, apply for production review. Google typically takes 3-7 days.

Common Mistakes to Avoid

1. Waiting for testers to find you — They won’t. Be proactive.
2. Using fake accounts — Google detects this and may ban your developer account.
3. Uploading a broken build — Fix all crashes before closed testing.
4. Ignoring tester feedback — Use it to improve your app before production.

Quick Reference