Capping IT Off

Capping IT Off

Opinions expressed on this blog reflect the writer’s views and not the position of the Capgemini Group

Testing Mobile Applications – Key Challenges and Considerations

With increased mobility and increased mCommerce, organisations spend significant time trying to understand consumer needs. Consumers have access to more and more data at their disposal to be able to make decisions. This has led to changed behaviors of consumers and ever increasing expectations. The end result is changed market dynamics of how we do business.

More and more enterprises are leveraging mobility to boost their top-lines, improve efficiencies and venture into new business areas and penetrate the markets.



Today, millions of mobile users depend on their devices and on their mobile apps. Mobile users are increasingly critique of user experience and performance of mobile apps. Increased usage of mobile apps also has increased the need of robust testing of these applications before releasing to market. It is required common challenges faced by mobile app users are addressed during testing of these applications.

Lets’ discuss key challenges encountered in use of mobile applications - as well challenges in testing these applications.

User Experience 
Success of mobile applications is primarily determined by user experience. User experience includes ease of navigation, speed of response, and defect-free transactions. User experience can be enhanced further with innovative and contextually appropriate experience. It is important to ensure existing bugs are addressed and new bugs are not regressed to prevent poor end user experience.

Contextual Appropriateness
Context can limit or extend the operation of mobile applications or its functionalities. Type of smart phones denotes changed environments and usage patterns that impact context.  Contextually appropriate data from the environment can enhance customer experience. Contexually different data and testing creates unique challenge in the testing process.

Varied Mobile User Interfaces
Different mobile operating systems like Android, Windows etc. have different user interfaces, in turn guided by specific rules and guidelines. The usage and layout of elements is checked in the verification process when publishing the mobile applications in the markets. Non-compliance with rules and guidelines can delay the publishing process; in turn impacting increase in the cost of development and testing.

Device Diversity and availability
The Number of the devices to be tested for compatibility is huge especially Android. Availability of all physical devices for different regions is high risk and investment. Remote testing adds more complexity to this aspect.

Device Based Testing Approach
Under the device based approach, there should be a testing laboratory set up which also involves purchase of real time mobile devices. It seems to be more costly than the emulation method as it takes care of verification of device based functions and other Quality of Service parameters. This method needs to cope with the rapid changes in the ever changing mobile devices and platforms.

Automated Testing of Layouts
Involves loading pages and images in renderer and compare the output with expected results. This is much beyond just layout and rendering and includes Pixel level test for image rendering & positioning. The test should be targeting smallest possible code fragment or feature. Layout test span across browsers and devices applications hence visual and rendering responsiveness testing should be one of the key testing considerations.

Test automation challenges with Non- standardized tools
Mobile Automation is evolving and there is variety of tools available in the market and Automation solution that runs across platform/OS/Devices is the need of the hour. The right tool selection and creating an robust framework is the challenge to addressed

Reduced Time to Market
Shrunk timelines to release the applications reduces available time for testing. Ample time needs to be planned for effective testing and later release. Security Issues Apps and devices managed via private cloud are much more secure than apps running in a public cloud. A secure private cloud can provide all the access to testing teams and there would be no data breaches whatsoever.

Key Recommendations Some of the key recommendations to enhance usability include –
(i) Test Early, Test Often
(ii) Test competitor products before developing your product
(iii) Test wireframe early in the development process
(iv) Test user journeys through live users for real customer experience
(v) Conduct cross-browser/cross-screen tests
(vi) Test on multiple platforms.

About the author

Renu Rajani
4 Comments Leave a comment
rrajani's picture
Hi, Good point about testing competitor's products
Good article, thanks for putting it together. I would add the challenge we are facing the most in mobile app testing: localization. We support 14 languages including right to left. Its hell lot of work to ensure every update goes accurate in all 14 languages. Biggest biggest problem is fitting the content for languages like german where nouns or verbs are too long. Screen diversity is like last nail in coffin. Can't suggest one find solution for this kind of situation but do lot of manual testing with local country people.
Hi Renu , You have very well elaborated the importance of user testing and the impact of it on the overall user experience.Test Early- test-often is a very nice point. Even i conduct lot of physical user testing and observe users through the critical lenses.It feels very import to observe closely the reactions of end users and amend mistakes much early . Very critical business need well spelt and articulated .
Very good points given. Also security quality testing is very crucial in the process that needs to be mentioned.

Leave a comment

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