Mobile Manual Testing: Gestures, Rotation, Interruptions
On this page
Everything in the previous chapters applies to mobile apps and mobile websites. Phones add a layer that desktop testing never sees: touch, small screens that rotate, an operating system that interrupts your app whenever it likes, and permissions the user can grant, deny or revoke at any time. This chapter is a field guide to that layer, organised as checklists you can copy.
Real devices, emulators and simulators#
Android emulators and iOS simulators are fast to start and good for checking layout and flows early. They are not phones: they run on desktop CPUs, use the desktop's network, have no real camera, cellular radio or biometrics, and iOS simulators run a different build of your app (compiled for the Mac, not for the device). Use them early, then do the release pass on real devices.
In TestingBot Live for apps you upload your build (.apk or .aab for Android, .ipa for real iOS devices, .zip for iOS simulators), or install from the App Store, Play Store or TestFlight, pick a real device or a virtual one, and control it from your browser. To review a mobile website rather than an app, choose mobile Safari or Chrome on a device in the web Live launcher instead.
Gestures and touch#
Mouse-driven testing hides most touch problems. Work through these on the device:
- Tap targets. Can you hit every button, link and checkbox reliably, including ones close together? Small icons in toolbars and table rows are the usual offenders.
- Swipe and scroll. Lists, carousels and swipe-to-delete: does a vertical scroll accidentally trigger a horizontal swipe? Does a carousel inside a scrollable page trap the scroll?
- Long press and double tap. Context menus, text selection and zoom; does double tap zoom when it should not, or not when it should?
- Pull to refresh at the top of every list that supports it, and on screens that should not refresh.
- Back navigation. The Android Back gesture or button and the iOS edge swipe on every screen, especially inside modals, multi-step forms and after a payment.
- Keyboard. Does the right keyboard appear (numeric for a PIN, email for an email field)? Does it cover the field you are typing in or the submit button? Does "Next" move to the next field?
On a remote device your mouse stands in for a finger: a click is a tap and a drag is a swipe. Multi-finger gestures such as pinch-to-zoom are the hardest to perform remotely; if pinch matters to your app (maps, photo viewers), include a check on a phone in your hand as well.
Rotation and screen sizes#
- Rotate on every screen of a new flow, not just the first one. Rotate mid-task: halfway through a form, with the keyboard open, while a video plays, during a loading spinner.
- After rotating back, is state preserved? Form input, scroll position, the selected tab and an open dialog should all survive. On Android, rotation recreates the screen by default, which is a classic source of lost input.
- If the app is portrait-only, confirm it stays portrait rather than rotating partly.
- Check the smallest and largest screens in your matrix, and a device with a notch or camera cutout: content behind the status bar or home indicator is a common release bug.
The Rotate button in the Live toolbar turns the device between portrait and landscape.
A sign-up form looks fine in portrait and in landscape. Which rotation test is most likely to find a bug that those two checks missed?
Layout in each orientation is one question; surviving the change is another. Rotation can recreate the screen, and unsaved input, focus and keyboard state are what get lost. The other two options repeat checks you have already done.
Interruptions#
Real users are interrupted constantly. For each critical flow (log in, pay, upload, record), interrupt it at the worst moment and check the app recovers:
- Send the app to the background and return, after a few seconds and after several minutes.
- Lock and unlock the screen mid-flow.
- Notifications arriving while a form is open; tapping one that deep-links into another screen.
- Switch apps to copy a code from email or SMS, then come back. Does the app still show the code entry screen with your input?
- Network changes: airplane mode during a request, Wi-Fi to cellular, a slow or flaky connection. The app should show an honest error and let you retry, not spin forever or submit twice.
- Incoming call or alarm during audio, video or a payment.
- Low battery and power saving modes, which throttle background work.
Not every interruption can be triggered on a remote device, and you should say so in your test notes rather than skip it silently. Incoming calls and cellular handovers, for example, need a phone with a SIM in your hand. Backgrounding, locking, switching apps and many network checks you can do anywhere.
Permissions#
Every permission (location, camera, photos, microphone, notifications, contacts) has at least four paths to test:
- First request, allowed. Does the app explain why it needs the permission before the system prompt appears?
- First request, denied. The app must still work for everything that does not need it, and explain how to enable it later. A blank screen or a crash here is a release blocker.
- "Allow once" or "only while using the app" (location on both platforms; photos have a limited-selection option on iOS). The next time the feature is used, the app has to cope with asking again or with a partial selection.
- Revoked later in Settings, while the app is in the background. Return to the app: does it notice, or does it crash on the next camera call?
Permission state sticks to the installed app, so make sure you start the "first request" paths from a state where the permission has not been decided yet; reset it in the system Settings or reinstall the app.
A delivery app asks for location on its first screen. Which permission test is most important before release?
The allowed path is the one developers try every day. Denying is a normal user choice, and if it leaves the user stuck, every privacy-minded customer is lost at the first screen.
Device state: location, language, appearance#
Many mobile bugs depend on device settings rather than on what you tap. The Live app toolbar covers the common ones:
- GPS Location sets a mock position that the app receives, for store finders, delivery zones and region-locked features.
- Locale changes the language and region of the whole device: check long translations, right-to-left layouts, date, number and currency formats.
- Device Settings switches between light and dark mode instantly: check contrast, images with transparent or white backgrounds, and text that is hard-coded to one colour.
- Copy/Paste syncs your clipboard with the device, handy for pasting one-time codes and long test data.
When something goes wrong, open DevTools in the session: Device Logs streams the device log in real time with filtering by level and search, and you can download it to attach to your bug report. App Inspection shows the element tree, which helps you describe exactly which element misbehaved. When you stop the session, its video and logs stay available in the member area. The Live test interface page lists every toolbar action.
Local backends on devices#
If the build you are testing talks to an API on your machine or a staging server, start TestingBot Tunnel and point the app at local.testingbot.com:<port> or your internal hostname, not localhost: devices cannot use localhost through the tunnel, and on iOS it is an operating system restriction. The App Live local testing page has the details.