Stop 09 · Mobile TestingTopics · 1/8

Mobile Testing Fundamentals

In short

A website lives on a desk. An app lives in a pocket: on a bumpy bus, at 4% battery, on patchy 4G, with WhatsApp pinging every minute. That's what makes mobile testing its own skill.

Testing mobile applications introduces unique considerations beyond web testing — device fragmentation, OS versions, network conditions, and app store review requirements all add complexity.

The purple blob pushes a small street food cart along a puddled road in the rain, holding up a phone.

Think of it like this

The street food cart vs the restaurant

A restaurant has a steady kitchen, fixed tables and a reliable power line. A food cart deals with rain, potholes, crowds and a gas cylinder that might run out. Desktop web is the restaurant. Mobile apps are the cart.

Watch it happen

Where mobile bugs come from

Mobile risks

Devices

Network

Interruptions

App stores

Sizes and OSes

Slow 4G, offline

Calls, battery

Review rules

1/5Mobile adds four kinds of risk that a desktop browser mostly doesn't have.

The big ideas

What you need to know

Native, hybrid, web

Native apps are built per platform. Hybrid apps wrap web code. Mobile web runs in the phone's browser. Each fails differently.

Network is a feature

Test slow, flaky and offline connections. Many users are on budget phones and patchy data.

Touch, not clicks

Swipes, long-press, pinch and the on-screen keyboard hiding fields are all mobile-only bugs.

Builds and installs

Fresh install, upgrade from an old version and uninstall each need a test.

See it in code

Walk through the code

bash

1# See connected Android devices and emulators2adb devices3 4# Install a test build (replace if already installed)5adb install -r app-debug.apk6 7# Save device logs while you test (Ctrl+C to stop)8adb logcat > test-session.log9 10# Take a screenshot for your bug report11adb exec-out screencap -p > bug.png

1/3Confirms your phone or emulator is connected and ready.

adb, the Android Debug Bridge, comes with Android Studio's platform tools. Every Android tester uses these daily.

Save yourself the pain

Common mistakes

Oops

Testing only on your own flagship phone on office Wi-Fi.

Do this instead

Include an older, cheaper device and a slow or unstable network in your test plan.

Oops

Testing only fresh installs.

Do this instead

Most users upgrade. Install the old version, add data, then upgrade and check nothing is lost.

Your mission

Explore an app like a mobile tester

~30 min

Quick check

Which test is most specific to mobile apps?

Go deeper

1List 3 testing considerations unique to mobile that don't apply to web testing.
2Learn the difference between testing a native app, a mobile web app, and a hybrid app.
3Understand why mobile testing generally requires more device/OS combination coverage than web.