How to Create a Closed Testing Track

Introduction

Before you can begin Google Play’s closed testing phase, you need to create a closed testing track in Google Play Console.

This testing track allows you to share your app with external testers under controlled conditions, helping you meet Google’s 12 testers for 14 days rule and qualify for production release.

In this guide, we’ll walk you through how to create a closed testing track properly — so your testing data is valid and recognized by Google.

Quick Answer / TL;DR

You can create a closed testing track in Play Console by:

Going to Testing → Closed Testing → Create Track.
Naming your track (e.g., Closed Testing 1).
Uploading your app bundle (AAB).
Adding testers via email list or opt-in link.
Saving and publishing the track to begin testing.

Once published, your app becomes available to selected testers through Google Play.

Step-by-Step: How to Create a Closed Testing Track

Step 1: Open Your App in Google Play Console

Go to Google Play Console.
Select your app from the developer dashboard.

🧭 If you haven’t created your app listing yet, do that first by clicking Create App and completing the basic setup.

Step 2: Navigate to the Testing Section

In the left menu, select Testing → Closed Testing.
Click Create Track.

You can have multiple testing tracks, but only one closed testing track is required for meeting Google’s production eligibility rules.

Step 3: Name Your Closed Testing Track

Give your track a clear and descriptive name — for example:

Closed Test - December 2025
Beta Testing Round 1

✅ Use a name that matches your project or testing goal. It will help you keep multiple rounds organized.

Step 4: Upload Your App Bundle (AAB)

Google requires apps to be uploaded as Android App Bundles (.aab) — not APKs — for testing and production.

Click Create New Release under your track.
Upload your .aab file or choose an existing build from your library.
Add release notes (optional but recommended).

💡 Make sure the uploaded build is stable and tested internally before you start closed testing.

Step 5: Review App Signing and Permissions

Ensure Play App Signing is enabled — it’s required for distributing test builds.
Also, confirm that your app permissions and policy declarations are complete before saving your release.

⚠️ Missing permissions or unreviewed privacy declarations can cause your release to be blocked.

Step 6: Add Testers

At this point, you can either:

Add testers manually by email, or
Create an opt-in link to share with external testers.

📘 You’ll learn both methods in upcoming articles:
“How to Add Testers in Google Play Console” and “How to Invite Testers via Email or Link.”

Step 7: Review and Publish Your Track

Once your tester list or link is configured:

Click Review Release → Publish Release.
Your app will become available to selected testers through Google Play within a few hours.

🚀 The testing phase officially begins once all testers opt in and install the app.

Best Practices

Use a distinct track name for each testing cycle.
Keep a stable build — avoid updates mid-test unless necessary.
Double-check policy compliance before release.
Monitor tester opt-ins and engagement through Play Console.

Common Mistakes to Avoid

❌ Uploading APKs instead of AABs.
❌ Starting closed testing before permissions are reviewed.
❌ Forgetting to publish the release after uploading.
❌ Confusing internal testing with closed testing.

Official Resources

Frequently Asked Questions

Do I need to create multiple testing tracks?

No. One closed testing track is enough for the 12 testers / 14 days requirement.

Can I run closed testing for multiple app versions?

Yes, but each track must complete the full testing cycle separately.

Does Google review my track setup?

Google doesn’t review the setup manually, but incorrect configurations can prevent testing eligibility.

Conclusion

Creating a closed testing track is the foundation of your Google Play testing process.
Once your track is live, you can start inviting testers, monitoring opt-ins, and tracking participation to meet Google’s requirements.

Ready for the next step?
Continue with How to Add Testers in Google Play Console — where you’ll learn how to assign your 12 testers and start the 14-day clock confidently.