Solving the Mobile Testing Conundrum
A global overview by WeAreSocial.com (2017) revealed that more than half of the world’s web traffic now comes from mobile devices. Additionally, Gartner states that by 2018, more than 50 percent of users will go to a tablet or smartphone first for all online activities. So, it is not surprising that today’s software development is based on a mobile-first, even if it is not mobile-only, imperative. But for all these dramatic changes, developers still struggle when it comes to mobile testing. In this feature, I set out the factors to consider when building an effective mobile test automation strategy and weigh up the benefits and disadvantages of popular test automation frameworks.
There are many factors that can make or break the success of a mobile app. For example, consider device fragmentation. Gartner says that in Q4 2016 there were 432 million smartphones sold in the world. Of that 432 million, 352 million run Android and 77 million run iOS. Those are just new phones - there are hundreds of millions of other devices running older firmware. When your app needs to work across most of these devices, it can become a serious burden for testers.
Another factor that contributes to this complexity is the device itself: varying screen and device sizes, resolutions and orientations. Next, we have multiple app types, such as web, hybrid and native. These multitudes of devices operate differently on various device and OS combinations. Finally, you have users all over the world in different regions that must be tested for translations, timezones and targets. These factors make testing with mobile a challenge.
Even though mobile testing is complex, it can be done successfully with the correct strategy. A sound mobile test automation strategy must include test automation frameworks, real devices, and emulators and simulators.
Download the white paper and learn how focusing on these three areas help organizations thrive in the fast-paced world of mobile software development.