In this guide
Games break differently from utility apps: state is large, sessions are interrupted, and "feels wrong" is a bug. Test on a low-end and a recent device. Each item has a reason and a check.
First minutes
1. Tutorial from a fresh install Why: most players decide here whether to stay. How to check: install clean, do not read your own notes. Can you finish the tutorial without help? Can you skip it, and can you replay it later?
2. Controls and touch targets Why: small or overlapping targets cause misses that feel like unfairness. How to check: play with thumbs only, in both hands, with a case on the phone. Try a small screen and a tablet.
3. Difficulty curve Why: spikes cause quitting, flat stretches cause boredom. How to check: note where you fail or get bored in the first levels. Give the build to someone who has never seen it and compare their stuck points to yours.
State
4. Save and restore Why: lost progress is the fastest way to a one-star review. How to check: progress, close the app from the app switcher, reopen. Repeat after a restart of the phone and after an update install over the old build.
5. Interruptions Why: calls, alarms and notifications arrive mid-game. How to check: during play trigger a call, a notification, lock and unlock, switch apps for a minute. Does the game pause, resume at the same point, and keep sound states? See interruption tests.
6. Offline and poor network Why: many games need a server only for some features. How to check: play in airplane mode. Which features still work, and is the rest explained rather than frozen?
Performance
7. Frame rate and heat Why: stutter and a hot phone end sessions. How to check: play 15 to 20 minutes on a low-end device in the busiest scene. Note stutter, heat and battery drop.
8. Memory and loading Why: crashes between levels often come from memory. How to check: switch between levels and menus repeatedly; background the game during loading.
9. Sound and haptics Why: unexpected audio is a top annoyance. How to check: test with silent mode on, headphones in and out, and Bluetooth audio. Check that music and effects have separate settings if you offer them.
Money and rules
10. In-game purchases Why: money paths must be correct and clearly explained. How to check: use the test purchase setup of your platform. Buy, cancel the purchase halfway, restore purchases on a second device, and check that the item arrives only once.
11. Currency and rewards Why: balance bugs and double rewards break the economy. How to check: complete the same reward action twice quickly, and after a restart. Does the balance stay consistent and match what the screen showed?
12. Age and consent screens Why: wrong or confusing prompts can cause trouble beyond the game. How to check: view each prompt for your target audience. This is a product check, not legal advice; ask a qualified person about requirements.
Related
- Hub: mobile app testing checklists
- E-commerce app testing checklist
- Audio and video playback testing checklist
Players you do not know find the stuck points you cannot see anymore. Start free and ask for private, structured feedback.