A few months ago, I commented on the findings from the research conducted for the World Quality Report which shows that a small number of organizations formally test their mobile applications. This is a topic that is increasingly gaining attention, although as a big challenge. We find that mobile solutions have pretty much followed the same path as web evolvement, quickly becoming a crucial element of how businesses run from the discovery phase.
It’s not surprising that a lot of organizations find mobile testing more of a challenge. Testing mobile applications can be also said to follow the trajectory of testing web applications, although some areas are more challenging. The device and platform related issues I mentioned previously are still there and maintain their importance. Applications not only need to work on multiple devices and frequently updated operating systems but they need to work well. User experience is crucial for the success of applications and there are particular characteristics to consider such as look and feel and navigation. Is the app intuitive? Can users easily find what they are looking for? How do we handle errors and inform users about them? Can the app cope with increased demand for access? Increasingly, end-users are using social media to comment on new apps providing developers with valuable feedback.
There are lots of questions to answer thus scenarios to test on platforms, user experience, performance, security, system integration and the app distribution. Even though all these issues make mobile testing seem like an overwhelming task, organizations can apply current testing approaches such as TMap NEXT® to mobile testing to overcome these challenges.
We have recently issued a paper to shed light on this particular subject and demonstrate how we adapted our methodologies to help you get the business value out of your mobile solution. It is a great read to learn more.