Ever since the first cell phone hit the commercial market in 1983, the mobile market has rapidly innovated from a handset that weighed over 2 pounds and could only make one phone call at a time, to a modern-day smartphone that weighs barely 5 ounces and can hold enough apps to practically run your entire life. In this course, uTest guest author Anand Ramdeo outlines ten ways that testing mobile apps differs from desktop and web testing, and points out the complexities and nuances that make mobile testing a unique skill for testers.
We have witnessed transition from desktop to web and are witnessing another transition from web to mobile. Before I delve deeper into the subject – it is important to understand how testing mobile applications is different from testing browser / desktop applications. If we understand the distinction and challenges of testing mobile apps, it will be a bit more easier to tackle them.
1. Supported platforms and devices mean you have more combinations to test.
Desktop apps were usually targeted for specific platforms and it was relatively easy to access those platforms. Web based applications made it a bit more challenging by adding another dimension: browsers.
Mobile applications take complexity of supported platforms to the next level by adding devices. Ensuring that mobile apps are working on all type of devices (smartphone, tablets, and phablets) supplied by major brands (various models from Samsung, Sony, Nokia, HTC, Apple, etc.) and on all the platforms (iOS, Android, Windows, BlackBerry, etc.) is challenging. On top of that, new devices are hitting market so often that it becomes impossible to cover all the major devices.
In the mobile world, it is important to create something on the lines of graded browser support used by Yahoo to ensure that major platforms are covered.