Start a project

Mobile app testing checklist for iOS and Android

3 min read

What to test in a mobile app before release, from install and sign-in to interruptions, poor signal, permissions and store rules, on real devices.

A hand holding a smartphone with a mobile app open, in front of a design monitor

A mobile app fails in ways a website does not. The phone rings mid-payment. The signal drops in a lift. The user refuses the location permission. Here is what we check before an app goes to the store.

Install, update, remove

  • A fresh install from the store or a test build
  • An update over the previous version, with the user's data still there afterwards
  • First launch with no account, and with an existing account
  • Removing the app and installing it again
  • Enough free space, and what happens when there is not

Updates are where data gets lost. Always test the path from the version your users have now to the new one.

Sign-in

  • Email and password, including a wrong password
  • Phone number with a one-time code, including a wrong and an expired code
  • Sign in with Google and with Apple
  • Forgotten password, start to finish
  • Staying signed in after closing the app and after restarting the phone
  • Signing out, and whether the next user can see the previous user's data

Screens

  • A small phone, a large phone and a tablet
  • Portrait and landscape, if the app allows rotation
  • The notch, the rounded corners and the home indicator not covering anything
  • The keyboard not hiding the field being typed in
  • Large system text and dark mode
  • Long names, long addresses and other languages not breaking the layout

Interruptions

This is the section most teams skip. In the middle of an important action:

  • Receive a phone call
  • Receive a notification and tap it
  • Switch to another app and come back
  • Lock the screen and unlock it
  • Let the phone sit until the app is put to sleep

After each one, the user should be where they were, with nothing lost.

Network

  • Wi-Fi, mobile data, and switching between them
  • A slow connection
  • No connection at all
  • Losing the connection halfway through a request

A good app tells the user what happened and keeps their work. A poor one shows a spinner forever.

Permissions

For camera, photos, location, notifications, contacts and microphone:

  • Allow it
  • Refuse it, and check the app still works and explains what is missing
  • Refuse it, then try the feature again later
  • Change the permission in the phone's settings while the app is open

Payments

  • A successful purchase in the store's test mode
  • A cancelled purchase
  • A failed payment
  • Restoring purchases on a new phone
  • A subscription renewing and being cancelled

Notifications and links

  • A notification arrives when the app is open, in the background, and closed
  • Tapping it opens the right screen
  • A link from an email or a message opens the app at the right place
  • The same link when the app is not installed

Battery, memory and speed

  • The app starts in a reasonable time on an older phone
  • Scrolling long lists stays smooth
  • The phone does not heat up or drain quickly in normal use
  • An hour of use does not slow the app down

Before you submit

  • The version and build number are correct
  • No test accounts, test servers or debug menus are left in
  • Screenshots and descriptions in the store match the app
  • The privacy details you declared match what the app collects

Test on real phones

Emulators are useful while building, but they do not have a real camera, a real radio, or a thumb. Interruptions, signal changes, performance and gestures need a real device. At minimum, test on one recent and one older phone for each platform.

We run this on real iPhones and Android phones as part of mobile app testing. If your app talks to your own server, the endpoints behind it are worth checking too: see API testing.

Chat with us