Deploying to Google Play Test Tracks

Welcome back! In the previous lesson, you successfully uploaded your signed Android App Bundle (AAB) to the internal testing track, a crucial first step for rapid, private feedback. You now have a build that your core team can install and verify.

Today, we will expand our testing scope by learning how to promote that build to the next stages in the release lifecycle: the closed and open testing tracks. This process is fundamental to gathering broader feedback and, for many developers, is a mandatory step before a full production launch. By the end of this lesson, you will understand the purpose of each track and be able to confidently move your application through Google Play's pre-release testing workflow.

1. The Strategy: Promote, Don't Re-upload

Once you have a build on the internal track that you've deemed stable, the most efficient way to move it to a wider audience is by promoting it. Instead of building, signing, and uploading a new AAB with a new version code for each track, you can simply push the exact same artifact forward.

This approach has several advantages:

• Efficiency: It saves significant time and reduces the chance of introducing errors between builds.
• Consistency: You are testing the exact same code across different user groups.
• Simplicity: It keeps your versioning clean and straightforward.

The PrimeTestLab article on Google Play testing tracks has an excellent section highlighting this as a key time-saving secret.

As the article describes, the action is straightforward. In the Google Play Console, you navigate to your internal release and use the "Promote release" option to select a new track.

Let's now explore the two main destinations for promotion: closed and open testing.

2. Promoting to Closed Testing: The Controlled Beta

Closed testing is the logical next step after internal testing. It allows you to test your pre-release app with a larger, controlled group of users. Unlike internal testing, builds submitted to the closed track go through Google's standard app review process.

The Mandatory Gate to Production

For many developers, this track is not just recommended—it's mandatory. Google has implemented a policy to improve app quality on the Play Store.

As detailed in the video, if your personal developer account was created after November 13, 2023, you must run a closed test that meets the following criteria before you can apply for production access:

• Have at least 20 testers opted-in.
• Those testers must be opted-in for at least 14 consecutive days.

This makes mastering the closed testing workflow essential for launching your app.

Setting Up and Promoting to the Closed Track

The process of promoting your internal build is simple:

1. Navigate to Testing > Internal testing.
2. Select the Releases tab and find the active release you want to promote.
3. Click the arrow next to "View release details" and select Promote release.
4. From the dropdown, choose Closed testing.

The Play Console will automatically carry over your AAB and release notes. However, you will need to configure the closed track itself, which is a one-time setup:

1. Navigate to Testing > Closed testing.
2. Go to the Testers tab. Here, you can create tester lists by email or manage access via Google Groups. This is where you'll add the emails of your 20+ beta testers.
3. Provide a feedback channel (URL or email address) for your testers.
4. Once configured, go back to your promoted release, click Review release, and then Start rollout to closed testing.

Important Consideration: The Review Time
Unlike the near-instant availability of internal tests, your first release to a closed track will be "In review" for a period that can range from a day to a week. The 14-day mandatory testing clock only starts after your app is approved and testers opt-in.

3. Promoting to Open Testing: The Public Beta

Open testing is the final pre-release stage. When you promote a build to the open track, its test version becomes publicly discoverable on the Google Play Store. Anyone can find it, join the test program, and submit private feedback to you.

When to Use Open Testing

It's crucial to understand that open testing is not a shortcut around the mandatory closed test. It is an optional tool that becomes available once you have production access.

Use open testing when:

• You want to run a large-scale public beta before a major launch.
• You want to test a new feature with a wide audience after your app is already in production.
• You are performing a "soft launch" in certain regions to gather data.

To promote a build (typically from the closed track) to open testing, the steps are the same: use the Promote release button and select Open testing as the destination. The main configuration difference is on the Testers tab, where you can either allow an unlimited number of testers or cap it at a specific number (minimum 1,000).

4. Version Codes and Tester Eligibility

Understanding how Google Play decides which version of an app to serve to a user is critical for managing multiple tracks. The logic is simple but has important implications.

Here's the key takeaway: a user always gets the app version with the highest versionCode from all the tracks they are eligible for.

This leads to a common pitfall:

• A user opted into your internal test is NOT eligible for your closed or open tests.
• If you promote a build with versionCode: 10 from internal to closed testing, and invite an existing internal tester to the closed test, they will still only receive internal test updates.
• If you then upload a new build with versionCode: 11 to the internal track, that tester will get versionCode: 11, even though the "more stable" build on the closed track is versionCode: 10.

To move a tester from internal to closed testing, they must first opt-out of the internal test program using their original opt-in link, and then opt-in to the closed test program with the new link you provide them.

Conclusion

You now have a complete picture of the Android pre-release workflow, from a quick internal check to a mandatory closed beta and an optional public beta. Promoting releases is the key to moving efficiently through this process.

Here are the main points we covered:

• Always use the "Promote release" feature to move a stable AAB from one track to the next without re-uploading.
• Closed testing is for a controlled beta group and is a mandatory step (20 testers for 14 days) for new personal developer accounts before you can apply for production.
• Builds sent to closed and open tracks undergo a formal review, which takes time.
• Open testing is an optional public beta for large-scale feedback, and it is not a shortcut around the closed testing requirements.
• A user's eligibility is critical; they must opt-out of a lower track (like internal) to properly opt-in to a higher one (like closed).

In our next lesson, we will consolidate everything you've learned about both platforms. We'll walk through the final steps of submitting your iOS application for App Store review and your Android application for Google Play review, completing your journey from web app to store-ready mobile application.