Some people think testing mobile apps is easier than testing web applications or desktop applications because most mobile apps tend to be less complex. However, just because something is less complex doesn’t mean we testers can relax and assume that it is bug-free. Here are some common areas for bugs to hide that mobile app testers usually overlook.
Have you missed any of the following?
1. Keyboard buttons, such as “Done”, “Next”, “Search”
Sometimes, your app provides an on-screen button and a keyboard button to perform the same action, for example, “Done”, “Next”, and “Search”. Don’t just test the on-screen buttons and forget about the keyboard buttons! Some users may tend to use the on-screen buttons whereas some tend to use the keyboard buttons.
Make sure your app works with both on-screen and keyboard buttons.
2. Mobile app gestures
Every mobile OS platform has gesture and multi-touch support so that users can perform tasks more efficiently. And these features keep evolving. Sometimes, your developers associate app-specific tasks with different gestures, but sometimes, your app inherits the standard gestures without you knowing. For example, swipe to remove a row in a table.
Even if a gesture is not associated with a task, you may still want to try it out.
3. “Back” or “Cancel” button
Make sure there is a “Back” or “Cancel” button and it is enabled in any workflows.
Your users may want to visit the previous screen or exit from the current workflow.
4. Switch phone orientation during screen loading
It is common for apps to crash when you rotate the phone orientation while the app is loading. This is caused by apps that don’t handle the objects or data population properly when instantiating or destroying a view, resulting in a crash.
Make sure the app has been coded properly and isn’t subject to this all-too-common crash.
5. App update and re-installation
When you test a new release, do you have app update and re-installation tested as well? Usually we are too busy with testing the new features and regression testing so we forget or skip testing app update and re-installation.
This is especially important if your app stores data in its local database.
You may think it is unlikely to find any critical bugs in these areas, but as a tester, you should never hold an assumption and overlook any seemingly-alright parts. If you did not test any of the areas mentioned above, test them and you may find some surprising bugs.
If you have anything to add to the list, feel free to leave a comment and share with us.