Read More

Year after year, the IT industry grows along with the technology that takes significant steps forward in the evolution process. According to the results of the World quality report 2014-15, the proportion of Testing in the IT budgets continues to rise – from 18% in 2012 to 26% in 2014. A lot of focus has also been placed on Mobile Testing and its requirements. More and more products aim for the mobile platform and bring the need of understanding the background of such process fast.

Some differences between Mobile and Desktop Applications:

  • Variety of screen sizes and resolutions for mobile devices
  • Amounts of RAM and CPU architecture that can be used
  • Mobile Device can use different network connections (2G, 3G, LTE, Wi-Fi, WiMAX) or even several simultaneously
  • Not all automation testing tools support testing of mobile apps.

Creating a Test Strategy

When designing a strategy for testing mobile apps, consider to cover such areas:

  • Device Selection: The market is full of different devices. You should choose the ones that are widely used, consider the popularity of a device platform and disadvantages that new devices bring to your test process.
  • Emulators: Emulators can be very useful for testing at the early stage of the app development or if you don’t have any devices yet. An emulator is software that enables a system to reproduce work of another system. It typically allows the host system to run software or use peripheral devices designed for the guest system. Use this approach only for quick and superficial checking of the app.
  • Physical devices: To simulate real-life scenarios, testing should always cover real devices. They give you more chances to find specific cases than emulating devices.
  • Cloud-based testing: Due to the fast evolution of cloud systems, now it is possible to use them for testing purposes. For your specific needs, a web-based mobile environment can be created. Cloud systems have a lot of positive sides such as accessibility, scalability, ease backup and recovery, the possibility of multi-device coverage at one time.
  • Automation vs. Manual Testing
    • If new functionality is added, first, test it manually.
    • If tests are done only a few times, do it manually.
    • If regression tests are repetitive, automated testing will be a perfect solution.
    • Scenarios that need a lot of time for running should be reviewed for the possibility of creating automation scripts for them.
  • Network access is a needed part of mobile testing. Validation of work on different network connections and protocols (2G, 3G, LTE, Wi-Fi, WiMAX, etc) is very important for mobile applications.


Providing 100% test coverage of an app isn’t a simple thing because different applications could have unique specifications that can change some approaches to testing processes. Reviewing and analyzing areas covered in this article can help you in designing a testing strategy for the first time or just provides you our point of view for the basics of such process.