"Back" should always do the same predictable thing. On Android there is a system back button or gesture; on iOS there is a back button and an edge swipe. Test the system action, not only your own buttons. Each item has a reason and a check.
Basic stack
1. Back through the main flow Why: back must retrace the path the user took. How to check: open the app, go three or four screens deep, then press back repeatedly. You should pass the same screens in reverse order and end at the start, not at a screen you never visited.
2. Back from the first screen Why: the last back press leaves the app, which is easily done wrong. How to check: at the main screen, press back. The app should leave or ask in a predictable way, and reopening should not show an odd state.
3. Tabs and bottom navigation Why: users expect each tab to keep its own place, or reset, consistently. How to check: go deep in tab A, switch to tab B and back. Is A where you left it? Then press back and note where it goes. It should be the same rule on every tab.
Dialogs and modals
4. Dialogs and bottom sheets Why: back should close the top layer first. How to check: open a dialog, menu or sheet and press back. Only that layer should close. Tapping outside should behave as designed.
5. Modal and multi-step flows Why: back in a wizard may lose entered data. How to check: in a form with several steps, enter data, go back one step and forward. Is the data kept? Back on step one should ask, not silently discard.
6. Unsaved changes Why: lost edits are the typical result of an unthoughtful back. How to check: change a setting or text and press back. Does the app save, ask or warn, as you decided, and does it say so clearly?
Entry from outside
7. Deep links and notifications Why: users arriving mid-app have no history, and back must still make sense. How to check: open the app from a link or notification straight to a deep screen, press back. It should lead to a logical parent, not close the app unexpectedly or loop.
8. Login and onboarding Why: back should not return users to a finished step. How to check: finish login, then press back. It must not show the login screen again. Do the same after onboarding and after a payment.
9. Redirect loops Why: a screen that redirects forward on arrival traps the user. How to check: from a screen that auto-redirects (for example after logout or a permission check), press back repeatedly. You must be able to leave.
State and system
10. Back after interruption Why: after restart or a returned app, the stack may be gone. How to check: go deep, send the app to the background for a long time or kill it from the switcher (the system may restore it), reopen and press back. See interruption tests.
11. Rotation and keyboard Why: orientation changes can rebuild screens and reset the stack. How to check: rotate the device on a deep screen, press back, and with the keyboard open press back once (it should close the keyboard first).
12. Double taps and fast presses Why: pressing back twice quickly may skip a screen or crash. How to check: press back twice quickly during a transition and check where you land.
Related
- Hub: mobile app testing checklists
- Test interruptions: calls, alarms and app switching
- Wording and typo review checklist for apps
First-time users take paths you never would. Start free and ask for private, structured feedback.