Register now for Android Dev Summit 2019!

Use testing tracks to get invaluable early feedback from users

  • Launch
  • Test

Use the Google Play Console to release early versions of your app for internal testing, or to trusted users for closed and open testing. Get the feedback you need to make improvements to your app before its full release.

Why it works

Testing your app gives you the opportunity to fix any technical or user experience issues with minimal user impact, so you can release the best version of your app to most users. Feedback from your test users won't affect your app's public rating.

Best practices

  • Make sure users can join the tests. Your testers will need a Google account or a G Suite account to join a test.
  • Run tests internally. Use the internal testing track to push your app to up to 100 internal testers in seconds. Run an internal test before releasing your app to the closed or open tracks. If needed, you can run internal tests concurrently with closed and open tests for different versions of your app.
  • Choose the appropriate external testing type. Closed testing groups should be small and test the least stable, experimental versions of your app. Run the open test with a larger group to test stable versions of your app that are near release.
  • Run closed tests for targeted user feedback. If you want to run a test with a smaller group or with specific users, run a closed test using individual email addresses or Google Groups. You can also invite selected pre-registered users to join these tests.
  • Scale your tests. Any user can join your open test by clicking a link, making it easy to scale the number of users you reach. You can also set a limit to the number of users that join.
  • Check your Android App Bundle version code. To make an app on the internal, closed, or open testing tracks available to testers, you must give it a higher version code than your production version.
  • Provide a channel for testers to send you feedback. For closed tests, offer testers the ability to provide feedback by email, through a website, in a message forum, or by another suitable mechanism.
  • Make sure your app is ready to be made visible on the Play store before running an open test. Users join open tests from the Play store listing, which means anyone can find your app. Your app will appear in Play search results. So your store listing should be as complete and final as possible.
  • Plan carefully when you make any changes to your app's Pricing & Distribution page. Changes here will affect your app's current and future production versions, as well as its closed and open tests.
  • Run concurrent tests on the same app. You can run an internal test, multiple closed tests, and one open test on your app at the same time. Just remember the version code rules when using different tracks.
  • Use the pre-launch report to spot issues. Opt in to the pre-launch report to discover any issues found in your default closed testing track and open testing track as your app ran on real devices in Firebase Test Lab.

Examples