Test the important paths
Check your mobile app’s main tasks, accounts, connected services and small-screen behavior before release.
Test what a person can actually finish. A good-looking first screen is only the start.
On this page
Use a short repeatable checklist
First launch: does the app explain what to do when there is no data?
Navigation: can you open a detail, go back and reach each main screen?
Forms: try valid, missing and unusually long input; check the keyboard does not cover the action.
Saved data: create an item, reopen the app and confirm it is still there when persistence is intended.
Accounts: sign in and out. Check that a different account cannot see another person’s private data.
Connected services: make one real request and check both success and failure states.
Layout: test a small phone, a larger phone, both target platforms and larger text where supported.
Give the agent a reproducible problem
Test the release build too
Use a native test build for capabilities unavailable in the preview and before submitting. Test the same build and configuration intended for distribution, including authentication, connected features and support links.