How to test when releasing an app on Google Play

1. About Each Test

1. Internal Testing

• You need testers’ email addresses, but they don’t necessarily need to be publicly available.
• You can register only your own email address.
• If possible, you can also ask family or friends to add their email addresses.

2. Closed Testing

• Uses Google Groups or Google Play User Lists (CSV of email addresses).
• However, you can also register only your own email address to test.
• You don’t need to prepare a large list initially. Starting with just yourself is fine.

3. Open Testing

• This is a test open to the general public via the store, allowing participation from anyone.
• It’s not commonly used in the initial stages; the typical progression is Internal Testing → Closed Testing.

2. What to Do If You Don’t Have External Testers

You don’t need multiple test accounts.
You can test your app by registering yourself as the only tester.

✅ Internal Test Release Procedur

1. Open Play Console and select your app.
2. Go to Release → Testing → Internal testing.
3. Under Manage testers, add your own Gmail address.
4. Save and click “Roll out” to publish the internal test.
5. Copy the “Opt-in link” generated by Play Console.
6. Open that link in Chrome (logged in with your tester Gmail).

After the internal test release

• Releasing an internal test does not automatically trigger email notifications.
• Display the “Test Link” in the Play Console’s “Tester Management” screen, copy it, and open it manually.
• You must share the link with other testers.
• The key point of internal testing is that the app is “in a state where functionality can be verified.” There is no requirement that all testers must complete verification before proceeding to production.
• If you are the only tester, simply installing the app via the link fulfills the requirement.

3. Android Device Testing and Alternative Methods

When submitting and publishing an Android app via Google Play Console, device testing requires an “Android device.” (Notifications, Ads SDK, and Google Play Services integration require physical devices.)

If you don’t have an Android device, the practical approach is: first test using an emulator → eventually acquire an inexpensive physical device (like a used Android phone) or verify using Firebase Test Lab.

What to Do If You Don’t Have an Android Smartphone

1. Use the Android Emulator (Android Studio)
   Install Android Studio on your PC to use the official Android Emulator.
   While you cannot install directly to the emulator via the Play Console test link, you can verify functionality by exporting the built .apk or .aab → converting it to apks → then using adb install.
   This allows you to check the UI and basic behavior.
2. Obtain a physical device
   When ultimately publishing to the store, it is strongly recommended to verify on at least one physical device.
   Reason: Certain behaviors cannot be replicated on an emulator (e.g., notifications, camera, sensors, Google Play Services integration).
   Many developers purchase one inexpensive used Android device (dedicated solely for testing).
3. Ask acquaintances or friends
   Instead of registering your own Google account as a tester, you can register a friend or family member’s Gmail address and have them install the app on their Android phone.
   This allows them to test on a real device and provide screenshots and feedback.
4. Use Firebase Test Lab
   This Google cloud service installs your app on real Android devices to perform automated tests and capture screenshots.
   It integrates with Google Play Console → Releases → Testing → Firebase Test Lab.
   Even without your own devices, you can perform basic functionality checks.

Testing Procedure Using an Emulator

1. Launch Android Studio.
2. Open Tools → Device Manager → Create Device.
3. Select a model (e.g., Pixel 7) and click Next.
4. Choose a system image with Google Play support (e.g., Android 14 or higher).
5. Download and finish setup, then start the emulator (▶︎ button).

Once started, you’ll have a fully functional Android environment running on your Mac or PC.

Make sure to choose a system image labeled “Google Play” so you can install apps directly from the Play Store inside the emulator.

Installing the Internal Test Build on the Emulator

Once the emulator is running, open the Google Play Store app inside it.

1. Open Play Store inside the emulator.
2. Log in with the same Gmail account that you registered as a tester.
3. On your computer, open the opt-in link from Play Console.
4. Copy the link and paste it into Chrome inside the emulator.
5. Tap “Become a tester” → “Open in Play Store” → Install.

Your internal testing app will be installed on the emulator just like on a real Android device.
You can take screenshots and perform functional tests normally.

4. Publishing Your App

Once internal testing is complete, you can skip closed testing and proceed directly to live release.

1. Final Checks

Ensure all items under “App Content” in the Play Console are green (completed).
Key items to verify:

• Data Safety
• Advertising ID declaration
• Content rating
• Target audience/Children’s content
• Privacy policy URL

2. Update versionCode and build

You must increment the version number by +1 from the internal test version.
Example: If internal test is 1.0.0+4 → Production is 1.0.0+5.

3. Create the production release

1. Play Console → Releases → Production → Create new release
2. Upload app-release.aab
3. Fill in release notes (e.g., Initial release v1.0.0)
4. Confirm country/region distribution settings (enable required regions. For initial release, “All countries and regions” is safe)
5. Save, then click “Review release” → “Publish to production” in the top-right corner

4. Selecting Release Mode

Google recommends a staged rollout for initial releases.

• Staged rollout (recommended): Initially distribute to 10% of users → Roll out to 100% after a few days if no issues
• Full rollout (immediate): Distribute to all users immediately (acceptable for small apps)

5. Post-Release Process

• It takes several hours to up to one day for the update to appear on the Play Store.
• After publishing, always check Android Vitals (crash rate/ANR rate) and the Pre-launch Report (automated test results from Google’s test devices) in the Play Console.
• If no issues are found, expand the staged rollout to 100%.