Mobile testing should reflect how people use an app: on different screens, with changing connectivity, and sometimes with accessibility settings enabled. Start with the workflows whose failure would matter most.
Test behavior and state transitions
Cover valid and invalid forms, empty results, navigation back, repeated taps, saved state, and interrupted requests. A test case should identify setup, action, expected result, and cleanup.
Test devices and accessibility
Use appropriate emulators or approved devices for supported operating systems and screen sizes. Check text scaling, focus, touch targets, screen-reader labels, and orientation if supported.
Watch performance and resource use
Look for slow startup, unnecessary network calls, large assets, blocked interactions, and excessive background work. Record the test environment so performance observations can be reproduced.
Keep test evidence safe
Redact personal information, tokens, and credentials from screenshots and logs. Document defects with reproducible steps rather than sensitive user data.