What to verify and how.
WHAT TO TEST AUTOMATICALLY
Business logic, as fast unit tests Data layer behaviour, including migrations Critical interface paths
WHAT TO TEST MANUALLY
Anything involving real devices, real networks and real conditions.
WHAT MOBILE-SPECIFIC SCENARIOS TO COVER
Rotation mid-task Backgrounding and returning after a long period Termination and relaunch Permission granted, refused, and revoked later No network, and slow network Connectivity lost mid-request Low storage Low battery and power-saving mode Largest system font size Upgrade from the currently released version
WHICH OF THOSE IS MOST NEGLECTED
Upgrade testing, and it causes the most damage.
WHY
It affects existing users, who have data, and a failure on launch is unrecoverable for them.
WHAT TO TEST ON
At least one modest device and one current device, per platform.
WHAT TO AUTOMATE IN A PIPELINE
Build, unit tests, static analysis, and a smoke test.
WHAT TO RUN BEFORE EVERY RELEASE
The full manual checklist, on physical devices.
WHAT TO KEEP
That checklist, written down and updated after every incident.
