Mobile Testing Basics
Learn what is different about testing on mobile — device fragmentation, touch gestures, network conditions, and mobile-specific bugs.
What you'll learn
- Understand what makes mobile testing different
- Test key mobile gestures and orientations
- Simulate poor network conditions
- Identify platform-specific iOS vs Android behaviors
Manual QAlessonsJump to another lesson
Mobile Testing Basics
Testing a mobile app is not the same as testing a website. The device is smaller, the network is flakier, and users touch the screen with their fingers instead of clicking a mouse.
Bugs You Only Find on Mobile
Mobile vs Desktop Testing
Desktop Testing
- Mouse and keyboard input
- Big screens with fixed sizes
- Stable, fast network usually
- Power always plugged in
- Few browsers to cover
- One orientation — landscape
Mobile Testing
- Touch gestures and soft keyboard
- Hundreds of screen sizes and densities
- Flaky networks — 3G, 4G, offline
- Battery drain and overheating matter
- iOS + Android + many OS versions
- Portrait and landscape both
VerdictMobile adds variables desktop never faces. Plan for all of them.
Quick check
Which of these bugs is only possible on mobile, not desktop?
Device Matrix: Which Phones to Test On
You cannot test every phone. Pick a mix across two axes: operating system and price tier.
Device Coverage Matrix
iOS Flagship
Latest iPhone Pro — best performance, newest iOS
Android Flagship
Samsung Galaxy S / Pixel Pro — newest Android
iOS Budget
iPhone SE or older supported iPhone — slower CPU
Android Budget
Entry-level Samsung A or Xiaomi — slow chip, old Android
Gestures You Must Test
Orientation Testing
Network Conditions
Mobile users are rarely on perfect WiFi. Test the mean cases.
- 1
Full WiFi
Baseline — everything should feel instant and smooth.
- 2
Slow 3G
Throttle the network. Does the app show loading spinners? Does it time out gracefully?
- 3
Flaky connection
Drop packets mid-request. Does the app retry? Does it show a friendly error instead of crashing?
- 4
Airplane mode / offline
Turn off all networking. Does the app tell the user they are offline? Does cached content still load?
- 5
Reconnect
Come back online. Does queued content sync? Does the app recover without a restart?
iOS vs Android Differences
iOS
- No system Back button — swipe from edge instead
- Permissions asked one by one when needed
- Keyboard has a 'Done' button at the top right
- Share sheet uses iOS sharing icon
- App Store review process is strict
Android
- Dedicated Back button / gesture at bottom
- Permissions can be grouped or asked upfront
- Keyboard varies by manufacturer (Samsung, Google)
- Share sheet looks completely different
- Play Store is more flexible but fragmented
VerdictThe same feature often needs two different designs — one per platform. Never assume iOS behavior will match Android.
Real Device vs Simulator
Emulator / Simulator
- Free and fast to launch
- Easy to test many screen sizes
- Good for layout and logic checks
- Cannot test real touch accuracy
- Cannot test real battery or heat
- Camera, GPS, sensors are faked
Real Device
- Shows real touch, real gestures
- Shows real performance and battery drain
- Catches bugs emulators miss
- Slower to set up and share
- Need a device lab or cloud service
- Absolutely required before release
VerdictUse simulators early for fast feedback. Always confirm on real devices before shipping.
Accessibility on Mobile
Practice: Order the Mobile Test Steps
A new feature just shipped to mobile. Put these test steps in the right order — from fastest/cheapest checks to slower/deeper ones.
- 1Verify on simulator — does the new feature load and function at all?
- 2Test on one iOS flagship and one Android flagship real device
- 3Rotate the device and test the feature in both portrait and landscape
- 4Throttle network to slow 3G and verify loading states and errors
- 5Turn on VoiceOver / TalkBack and check accessibility
- 6Test on a budget Android phone to catch performance issues