Mobile app testing verifies that applications work correctly across the chaotic reality of mobile: thousands of device models, two evolving operating systems, unreliable networks, and interruptions arriving at any moment. This checklist covers the twelve areas a complete mobile QA pass must address.

1–6: Functional and Platform Coverage

1. Core functional flows — every critical user journey on both iOS and Android: onboarding, login, primary tasks, payments
2. Device fragmentation — test on a representative matrix: small/large screens, old/new OS versions, low-end/high-end hardware. Analytics should drive the matrix — cover the devices your users actually own
3. Interruption handling — incoming calls, notifications, alarms, low-battery warnings mid-flow; the app must resume gracefully
4. Network conditions — 3G, packet loss, airplane-mode transitions, switching Wi-Fi to cellular mid-request; offline behaviour and data sync on reconnect
5. Permissions — every permission denied, granted, then revoked mid-session: camera, location, notifications, contacts
6. App lifecycle — backgrounding, force-kill and relaunch, OS-initiated process death with state restoration

7–12: Quality Attributes

7. Performance — cold start time (target under 2 seconds), scrolling smoothness, memory footprint, battery drain over a typical session
8. Usability and accessibility — touch target sizes, screen reader support (VoiceOver/TalkBack), dynamic font scaling, dark mode
9. Security — secure storage of tokens, certificate pinning, no sensitive data in logs or screenshots, biometric auth flows
10. Installation and updates — fresh install, upgrade from previous version with data migration, uninstall/reinstall
11. Localisation — text expansion in longer languages, RTL layouts, locale-correct dates and currency
12. Store compliance — App Store and Play Store guideline checks before submission; rejection costs a release cycle

Automating Mobile Testing

Mobile automation typically uses Appium, Espresso (Android), or XCUITest (iOS) for native apps. For responsive web apps and progressive web apps, browser automation with mobile viewports covers most scenarios — a regression suite in TestInspector can run critical flows in mobile-sized browsers on a schedule. The economics of what to automate follow the same logic as our manual vs automated testing guide: automate stable repetitive flows, keep exploratory and device-feel testing manual.

Real-device coverage matters: emulators miss hardware-specific defects (cameras, sensors, manufacturer Android skins). Most teams combine emulator-based automation with manual passes on a physical device lab — or outsource device coverage, as described in our QA outsourcing guide.

Frequently Asked Questions: Mobile App Testing

How many devices should we test on?
Use analytics to cover 85–90% of your active user base — typically 8–15 device/OS combinations. Add one low-end device even if rare, since performance defects appear there first.

What is the difference between emulator and real-device testing?
Emulators are fast and cheap for functional flows; real devices reveal hardware, performance, and manufacturer-specific defects. Use emulators for breadth, real devices for confidence.

Should mobile web and native apps be tested the same way?
Mobile web testing focuses on responsive layout and browser compatibility; native testing adds permissions, lifecycle, store compliance, and device hardware. The functional core (does the flow work?) is shared.

How do you test push notifications?
Verify delivery in foreground, background, and killed states; deep-link landing on tap; notification permissions denied; and behaviour with multiple stacked notifications.

Need full-coverage mobile QA across iOS and Android? Explore Astaqc's software testing services or contact us.