Upload your Build file to Google Play Listing

Google Testing Tracks are different testing phases that allow you to test your app and "promote" it through various sets of users before releasing it to the general public.

Before You Begin

• You must test an app before you can release it to production.

• .AAB files cannot be installed directly to the User's Device for testing.

• Using Play Console, you can create releases on three testing tracks before you release your app to production. Each phase of testing helps you gather the feedback you need to make improvements to your app throughout its development.

• Testing your app allows you to fix any technical or user experience issues with minimal user impact, so you can release the best version of your app on Google Play.

Testing Tracks

You can think of these tracks as increasing levels that you "promote" your app release through. For instance, you might start with Internal Testing with some handpicked users, then move that build to Closed Testing, then to Open Beta Testing, then finally to Production.

1. Internal Testing: Allows you to share your app with up to 100 testers for initial quality checks

   • You can run internal tests while your closed and open tests are in full swing. This comes in handy when you're trying out different versions of your app with different groups of testers.

   • Test apps that are not fully set up.

2. Closed Testing: Allows you to test pre-release versions of your app with a wider set of testers to gather more targeted feedback.

   • You can create a total of 200 lists, and each list can have up to 2,000 users listed by by email address. You can create up to 50 lists per track.

3. Open Testing: Allows Users to search the app on Google Play before release. Before choosing this option, make sure your app and store listing is ready to be visible on Google Play.

   • For early access apps (new apps that haven't been published to production): Users can find your open test via search on Google Play. Once users find your listing, they can install and use your app.

   • For apps with a live production version: Users can opt-in to your open test from your store listing.

All tracks above Internal Testing must be reviewed by Google before being available to users. You can see the review status of your apps in the All Apps Dashboard of Google Play Console

Walkthrough

For this example, we're going to add testers and load our build to a new Internal Release.

Create Release

1. Open Play Console and go to the Internal testing page (Testing > Internal testing).

2. Click Create New Release.

   

   The initial release will be for the Internal Testing Track.
3. Let Google generate an app Signing Key for your app.

   

   
4. Now that you've generated a Signing Key, click on Upload to select and upload the .AAB build file generated by Adalo.

   

   .AAB files cannot be installed directly to your phone. Instead, you must use the testing tracks provided by Google.
5. Give your release a name. This name is only visible to you and is usually automatically filled when you upload your build file. You can also add notes about new features or bug fixes in the Release Notes section. When you're done editing, click Save.

   
6. When you're ready to send your release to the users of the release track (internal, closed, open, or production), click Review Release, then Start Rollout to _______, then click Save. Naturally, you'll want to review any warnings or Errors with your app.

   

   Some warnings are normal for Adalo apps and will not prevent you from publishing your app.
7. Next, we'll add some testers for our Internal Testing track.

Add Testers to Release

1. Locate the release and click on the Testers tab, then click Create Email List

   
2. Give your list of tester emails a name.

3. Add tester emails one at a time, or you can upload a .CSV file of user emails (make sure you add your own email!).

   
4. When done adding users, click Save Changes in the lower right corner, then click Create to acknowledge that this email list is available to all of your apps.

5. Ensure that the email list is selected as a test group.

6. Add a URL link for your users to send feedback to if you wish.

   
7. When done, click Save Changes in the bottom right.

8. Copy the URL and share with your testers!

Promote Release

Once you have tested the app release in a given track (in this case Internal Testing), you can promote the release to the next highest track or even skip tracks altogether and go straight to Production.

1. Find the release in its testing track, then click the Promote Release dropdown under the release and choose the track you wish to promote it to.

   

2. Add testers to new track.

3. For all tracks above Internal Testing (including Production), you will also need to assign the Countries and Regions where the app release will be made available.

   1. Click on the track's tab in the left-hand menu, then Manage Track (if applicable).

   2. Click on the Countries/Regions tab and click Add Countries/Regions.

   3. After selecting the countries and regions, click Add Countries/Regions in the lower right, then click Add.

When you are ready to promote the release to production, follow this guide!

Help

Stuck creating a new release?

Check out our Troubleshooting New Android Release Section for help with the most common issues when uploading a new release!

Learn More

Read more about the different testing tracks and how to move through them in this Set Up Guide from Google!