Android app testing: devices, versions and checks

Android runs on a very wide range of phone models, several recent system versions and many screen sizes. You cannot test them all, and you do not need to. What you need is a map of risk areas and a small set of devices and testers that covers them.

Start with the risk, not the device list. Ask what is most likely to break: the layout on a small or large screen, a permission the user refuses, the app being closed in the background, a weak connection, a different language, an update over old data. Each of those has a short check, and each check needs only a few devices to run well.

A practical split: use an emulator for quick checks of screen sizes, versions and languages. Use a real phone for performance, battery, camera and anything touching hardware. Use real testers for devices you do not own and for the way ordinary people use the app. Which Android devices to test on explains how to pick a small, varied set.

This page sorts the guides and checklists by situation. Pick the heading that matches where you are, and work through the pages in it. If you are preparing a Google Play launch, also see the hub on Google Play closed testing and the general mobile app testing checklist.

Guides

• Android vitals: the numbers worth watching Which stability metrics Play Console shows and how to use them next to tester reports.
• App signing and testers: what changes in test builds Why signing differs between local, upload and Play-delivered builds and what it breaks.
• How testers send an Android bug report Plain steps for capturing and sending a system bug report when something crashes.
• Play Console pre-launch report: what it checks How to read automated pre-launch results and decide which findings matter. Verify scope in current docs.
• Prepare test data and accounts for testers Give testers realistic content without exposing real users: seed data and safe accounts.
• Test camera, photo and media features on Android Device differences hit camera features hardest. A test list for capture, picker and upload.
• Test language and region on Android How to switch language and region quickly and what to check in formats, plurals and layout.
• Test the upgrade path from an older app version Install the old build, create data, update and verify nothing breaks.
• Test your app on tablets and foldables Large screens expose layout assumptions. A practical test set and what to look for.
• Testing Android screen sizes: phones, tablets and foldables A small set of screen sizes that exposes layout bugs, and tester instructions to check them.
• Which Android versions to support: a decision method Choose the minimum version from your own data and risk, not from folklore. Where to find your numbers.
• adb basics every app tester needs Install builds, clear data, grant permissions and capture logs with a handful of commands.

Checklists

• Android dark mode testing checklist A checklist for contrast, images, status bar, dialogs and forced-dark behavior in dark mode.
• Android large font and display size test Test layouts with the largest font and display size settings and fix clipped text and overlapping buttons.
• Android permissions testing checklist Grant, deny, revoke and re-ask: the sequences to run for every permission your app uses.
• Android release checklist: from build to rollout A pre-release checklist covering build, signing, listing, testing and staged rollout.
• First launch checklist for Android apps What a new user sees in the first minute: permissions, loading, empty states, offline first run.
• TalkBack test script for Android apps Gestures and checks to run a screen reader pass on Android. Complements the 10-minute general test.
• Test gesture vs three-button navigation on Android Check that bottom content, back gestures and insets work in both navigation modes.
• Test process death and state restoration on Android How to simulate the system killing your app and check that the user returns to the same place.
• Test screen rotation and configuration changes What can break on rotation, language or font changes, and a quick way to check each.
• Test switching between Wi-Fi and mobile data Ask testers to switch networks mid-task and check that requests, uploads and sessions recover.
• Test text input, keyboards and autofill on Android Input issues are common: hidden fields, autofill, long text and different keyboards.
• Test widgets and app shortcuts on Android Check widget updates, tap targets and shortcut behavior across launchers.
• Test your app in split-screen and multi-window A short list to catch state loss and layout issues when the window size changes.
• Test your app under battery saver and Doze What changes under battery saver and how to check alarms, sync and notifications.