How to Run a Closed Test for Your Android App

Updated on 4. September 2024 by Jan Bunk

A humanoid robot unlocking a door, digital art

You are viewing a preview of this guide. Please log in to complete it!

To unlock the production page, you need to first complete a closed test of your app. This guide will lead you through that so you can publicly release your app in the Google Play Store afterwards.

Go to the closed testing page.Go to the closed testing page.

Usually there should already be an existing track. If not, create one. Afterwards, click "Manage track".

Usually there should already be an existing track. If not, create one. Afterwards, click "Manage track".

Go through the steps one by one, starting with selecting countries.

Go through the steps one by one, starting with selecting countries.

We recommend adding all countries, so you can have testers from all around the world, which makes it easier to find 20 people.

We recommend adding all countries, so you can have testers from all around the world, which makes it easier to find 20 people.

Click "Save" at the bottom right.

Continue with the next step: "Select testers".

Continue with the next step: "Select testers".

Click "Create email list"

Click "Create email list"

Enter a name for your group of testers. Afterwards, you can add them by their Google account e-mail address, so usually their Gmail e-mail address.

You can either enter each e-mail one by one, or enter multiple e-mails separated by a comma, like abc@gmail.com,def@gmail.com

Make sure you press the enter key after filling out the e-mail field.

A screenshot of the fields where you enter a title and the e-mails for your testers.

Google requires that you have at least 20 testers who download the app and keep it installed for 14 days. Only then will you be able to publish your app in the Google Play Store. Because of that, try to add as many people as possible. Of course you should ask the people beforehand whether they are open to helping you test your app. The testers don't need to be employees of your company, it can for example be your friends, family or customers. They just need an Android device and you must have their Gmail address so you can add them here.

We work together with a company that offers to install your app on 20 devices for 14 days (which fulfills Google's requirements) for a one-time fee of $25 (excluding tax). If you can't find 20 testers yourself, you can order this service here.

In the next field you can enter your e-mail address, so your testers know where they can contact you about app issues.

A screenshot of the feedback e-mail address field.

In the section about how testers can join your test, use the option to copy the link where your testers can join the test. Save it somewhere so you can find it again later.

Click "Save" at the bottom right.

Tick the checkbox next to the list of testers that you just created.

Tick the checkbox next to the list of testers that you just created.

Click "Save" at the bottom right.

Click "Create new release" at the top right.

Click "Create new release" at the top right.

If you see the option, click "Choose signing key".

Click "Choose signing key"

Then choose "Use Google-generated key".

Click "Use Google-generated key"Download your app as an .aab file

Upload the .aab file you just downloaded in the Google Play Console.

Upload the .aab file you just downloaded in the Google Play Console.

After uploading the file you should see it listed below the upload field.

After uploading the file you should see something like this screenshot.
If you see the error message "Version code x has already been used. Try another version code.", please reload the page and instead of uploading the app bundle again, click "Add from library" and select it there.

Enter a description for the app release, for example "Initial release of the app.".

Enter a description for the app release, for example

Click "Next" or "Save" at the bottom right.

Click "Next" and "Save" at the bottom right.

Click "Go to overview"

Click "Go to overview"

Send the changes to review.

Click "Send 2 changes for review"

After Google has reviewed your app (this can take a few days), your testers should be able to access it using the link you saved in an earlier step.

If you see reports of errors in the app like in the following screenshot, you can ignore them, those are normal. If you actually see issues in your app, you can contact us of course.

A screenshot of the Play Console showing an error.

Please wait until the 14 day closed testing period is over before you click the button below, so you can still view this guide if necessary.

My 14 day closed test is completed.

Once you've completed all the steps in this guide, please click this button so you can continue with the next guides.

Author Jan Bunk
Written by
Jan Bunk

Hi, I'm Jan! I created webtoapp.design in 2019 while studying computer science in university. A lot has changed since then - not only have I graduated, but it's also no longer just me running webtoapp.design. We've grown to a global, fully remote team and have gathered lots of experience around app development and app publishing. We've created and published hundreds of apps in the app stores, where they've been downloaded millions of times.