← QA Library
Chapter 6 / 9 · 7 Min. Lesezeit

Mobile testing

What makes mobile apps different, how to choose devices, which checks matter most and how releases to the stores work.

Mobile apps run on thousands of device models, in pockets, on trains and with a battery that's always running out. That environment creates whole categories of bugs that never appear on a desktop.

Types of mobile apps

TypeBuilt withTesting focus
NativeSwift/Kotlin, per platformPlatform behaviour, performance, OS versions
Cross-platformFlutter, React NativeConsistency between iOS and Android, native modules
HybridWeb view inside a native shellWeb rendering, offline behaviour, bridges
PWAWeb app installable from the browserBrowser support, caching, push support

Choosing devices

You can't test on every device, so build a coverage matrix from real data: analytics of your users or market statistics for your region. Cover the most popular models, the oldest supported OS version, the newest OS (including betas before major releases), a small screen, a large screen or tablet, and at least one low-memory device. Use cloud device farms to extend coverage when needed.

Emulators and simulatorsReal devices
Fast, free, easy to automateReal performance, battery, heat and sensors
Good for layouts and early functional checksReal camera, GPS, biometrics, push notifications
Can hide device-specific bugsRequired before every release

Checks that matter most on mobile

  • Interruptions: incoming call, alarm, notification, switching apps, locking the screen mid-action
  • Network: Wi-Fi to mobile data, airplane mode, slow 3G, losing the connection during a payment or upload
  • Permissions: camera, location, notifications — granted, denied, and revoked later in settings
  • Lifecycle: app killed by the system in the background, then restored with state intact
  • Orientation and screen: rotation, notches, split screen, dynamic font sizes, dark mode
  • Resources: battery drain, heating, memory, storage full
  • Push notifications and deep links: open the right screen, logged in or not, app closed or open
  • Updates: upgrading from the previous version keeps user data and settings

Useful tools

# Android Debug Bridge (ADB)
adb devices                         # list connected devices
adb install -r app-release.apk      # install or reinstall a build
adb logcat | grep com.example.app   # read app logs
adb shell am start -a android.intent.action.VIEW \
  -d "myapp://orders/1042"         # test a deep link
adb shell screenrecord /sdcard/bug.mp4   # record the screen

On iOS, testers usually install builds through TestFlight and use Xcode to read device logs and run simulators. Proxy tools such as Charles or Proxyman help inspect API traffic from the phone.

Getting builds and releasing

Test builds are distributed through TestFlight, Google Play internal testing or Firebase App Distribution. Before submitting to the stores, check the store listing and screenshots, privacy declarations, in-app purchases in sandbox mode, and that the version number and release notes are correct. Store review can reject an app for crashes, broken links or missing account deletion, so a final smoke test on the release build is a must.

Test the update path, not just fresh installs. Most of your users will update an existing app, and data migrations are a classic source of release-day crashes.