Test and release overview

The Test and release overview page in Play Console gives you a high-level summary of your app's testing and release performance. It is designed to help you quickly understand how your latest releases are performing, see the status of all your testing tracks, and find actionable recommendations to improve your app's quality before your next release. Data on the page is displayed for a specific form factor, and you can switch between form factors (like Phones, Tablets, or ChromeOS) using the selector at the top-right of the page.

This page can be reached either from the Dashboard page or by expanding Test and release in the left hand navigation bar.

Understand the page structure

The Test and release overview page is organized into sections to give you a clear and prioritized view of your app's release health. At the top, you'll see key performance metrics for your most recent release, followed by an overview of your testing tracks, and finally a list of personalized actions to take for your next release

Publishing overview

At the very top of the page, a banner displays the current status of your publishing queue. This is the same publishing widget that appears on your App dashboard and provides a quick summary of any changes that are in review or ready to be published

Understand your latest release performance

This section gives you a snapshot of how your latest production or active open testing release is performing. Its goal is to provide the most important health metrics at a glance.
  • If you have an active Open testing release or an active Early access release (available to select Play partners), their stats will also be displayed.

For each release, you can see the following key metrics:

  • Release rollout status: The percentage of your users who have installed this release version.
  • Total release installs: The number of new installs for this specific release version.
  • Install base %: The percentage of your app's total install base that is on this release version.
  • Total app installs: The total number of installs for your app across all versions, for context.
  • User-perceived crash rate: Your release's user perceived crash rate compared to all of your app's other releases.
  • User-perceived ANR rate: Your release's user perceived "App Not Responding" rate compared to all other releases.

For crash and ANR rates, the data granularity will automatically default to hourly for the first few days of a new release to help you spot issues quickly, and will then switch to daily. You can click on any metric card to navigate to the relevant page for a more detailed analysis.

Manage your testing tracks and tools

This section provides a centralized hub to see the status of all available testing tracks and tools. It helps you see what you're currently using, monitor active releases, and discover tools you might not be using yet.

Each track or tool is displayed in its own card:

  • Internal app sharing: Quickly share app bundles with your team and testers using a generated link, without needing to create a formal testing track. This is useful for ad-hoc sharing and iterating on early versions of your app.
  • Internal testing: Distribute your app for initial quality assurance checks to up to 100 internal testers; testers can install paid apps for free.
  • Closed testing: Test pre-release versions of your app with a wider set of testers to gather targeted, private feedback. You can run multiple closed tests at the same time for different features.
  • Open testing: Run a test with a large group and make your app's test version discoverable on Google Play. Anyone can join your open testing program and submit private feedback.
  • Early access (available to select Play partners): A pre-launch testing program for eligible partners that offers advanced features, such as running multiple tracks and automatically moving testers to the production version upon launch.
  • Pre-registration: Build excitement and awareness for your app or game before it launches by allowing users to pre-register.

When a track is in use, its card will show key information like the release name and date. If a track is not in use, the card will explain its benefits and provide a clear call-to-action to help you get started.

Prepare for your next release

The For your next release section provides a prioritized list of issues, warnings, and opportunities to address before you publish your next update. This list is personalized to your app to help you focus on the most important items to ensure a high-quality, compliant release.
Understanding action item severity
Action items are categorized by severity so you can immediately understand their importance.
  • Errors (Blocking issues): These are critical issues that you must fix, you will not be able to send a new release for review until these issues are resolved. An example is a missing Data safety declaration.
  • Warnings (Needs attention): These are important issues that require your attention, such as security vulnerabilities that must be fixed by a certain deadline, or a note from an SDK provider that an SDK version you're using is outdated. While they may not block your current release, they might block future releases if not addressed.
  • Recommendations: These are opportunities to improve your app's technical quality, user experience, or release process. These are not mandatory but are strongly encouraged.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Main menu
442659694110798501
true
Search Help Center
true
true
true
true
true
92637
false
false
false
false