Pre-launch Reports vs Closed Testing: What's the Difference?

Two Different Types of Testing

When you upload an app bundle to the Google Play Console, you will notice that Google automatically generates a "Pre-launch report." Many developers confuse this automated report with the mandatory Closed Testing requirement.

They serve two entirely different purposes.

1. The Pre-Launch Report (Automated)

The moment you upload an AAB to any track, Google's Firebase Test Lab takes over. Google deploys automated bots to install your app on various virtual devices.

• What it does: The bots click random buttons for a few minutes to see if they can trigger a fatal crash. They also scan your UI for accessibility issues (e.g., "touch target too small") and security vulnerabilities.
• The limitation: Bots cannot read, understand context, or log into complex accounts. They cannot tell you if your app is actually fun or useful.

2. Closed Testing (Human)

This is the mandatory 14-day phase requiring 12 real people.

What it does

It validates the human experience. Does the app make sense? Do the features work as intended over a two-week period? Are users returning to the app?

Why You Need Both

You cannot use a clean Pre-launch report to skip the 14-day Closed Test. Google requires both the technical validation of the automated bots AND the behavioral validation of real human testers to grant production access.