Last Updated Jun 30, 2011 — App Management expert
Tips and strategies for testing mobile applications
App ManagementIf you want to deliver quality mobile applications that are first-to-market, only best practices in business and engineering will do.
Delivering a great user experience in a mobile application, be it a game or data analysis program, starts with well defined requirements and a complete application vision.
The Quality Assurance team must be involved early, reviewing user stories and writing test plans.
Well defined requirements expressed as user stories are a great place to start. If your system/customer analyst gets these right the use-cases will be simple and the work flows natural and intuitive. A complete vision of the application is an organic manifestation of minimizing the number of user actions required to walk through each user story.
Clear and easy to follow positive based test-cases should come directly form well defined use cases. Negative and edge test cases should also be easy to create. If not, some additional requirements gathering from stake holders will be needed and these additional requirements should be added to the user story.
Every test case should be autonomous. There should be no dependency on the order in which they are executed. If a test requires particular application state, add this information to the precondition or handle it in your setup method if it is automated.
A great mobile application user experience is never an accident, but rather the result of clear requirements, application vision and rigorous testing at the unit, integration, UI and service API level.
The prize for doing it right is confidence and pride in the application folks will download to make their lives a little easier and/or a little more fun.