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, and get feedback to make improvements before full release.

Why it works

Testing your app within your organisation or with users gives you the opportunity to fix any technical or user experience issues before you release it widely. You can then be confident about releasing the best version of your app to the rest of your 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 to have a Google account (@gmail.com) 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 you release your app to 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 when you know which users you want to test your app, run a closed test using individual email addresses, a Google+ community, or Google Groups.
  • Add scale to your tests. The open test can be joined by any user with a link in just one click, which means you can scale the number of users you reach. You can also choose a maximum limit to the number of users that join.
  • Check your Android App Bundle version number. For an app on the internal, closed, or open testing tracks to be available to testers, it must have 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, at a website, in a message forum, or through 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 your app’s Play store listings. However, it also means anyone can find your app, for example, it appears 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, and 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 concurrently. Keep in mind 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 for your default closed testing track and open testing track while running on real devices powered by Firebase Test Lab.

Examples