Mobile Test Strategies

In the process of developing applications for mobile devices, professionals are finding that the traditional methods of testing do not always apply. A recent white paper published by Macadamian outlines some key areas to be aware of.

When planning your testing effort for a mobile device application, in addition to the usual functional testing, it is also important to consider the following areas and how they differ from desktop or regular web applications:

  1. User Interface Testing – mobile devices have unique user interfaces like smaller screens that can be re-oriented, touchscreens and soft keyboards, and navigation methods like hard keys and trackballs.
  2. External Factors Testing – mobile device applications must also contend with interactions and interruptions from other device features like various network connection types, SD cards, phone calls, and assorted device settings.
  3. Stress Testing – mobile device applications have much less overall device memory and power available so must handle themselves very efficiently.
  4. Security Testing – mobile device security will become more and more important as the user base grows, so it is essential to test the security of your mobile web applications, sensitive data storage, and how your application behaves under various device permission schemes.
  5. Emulator Use – Emulators can be a great asset when it comes to achieving testing coverage on multiple devices, but your test plan must also respect the fact that sometimes there is just no substitute for the real thing.

I recommend downloading the paper and I am looking forward to additional papers on usability testing for mobile they are planning on publishing.

2 thoughts on “Mobile Test Strategies

  1. at this time, there is not specific software for mobile testing, but it is in development at several places. I have had some success creating mobile profiles in Morae and Silverback, but it requires some tinkering to record correctly.

Leave a Reply

Your email address will not be published. Required fields are marked *