We’ve been doing a lot of mobile applications testing this past year. It seems the rage as enterprise players move their applications to mobile and new players with such low barriers to entry to can get in the game with little up front investment.
Based on our experience, the skill level needed for mobile testing may be higher than traditional software testing. In addition to all the characteristics and complications added by the mobile platform, some coding or understanding of coding may be needed. For instance, some tools access application source code, so understanding development environments (Eclipse /Android SDK, Xcode/iOS SDK) is needed. In addition, knowledge of browsers and different rendering engines and their effect is also required.
Independent of what platform, you need to approach mobile testing with general software testing basics. Even if you specialize in mobile application testing, you still need to know software testing principles, techniques, test case design, and so on. These basics can then be adapted to the peculiarities and special considerations needed for testing MobileApps. Besides the knowledge of software testing basics, the following skills are also required for a good MobileApp QA:
- Familiar with mobile operating systems because when doing test scenarios for automation, the tester has to know whether the step can be simulated with the provided API of the mobile operating system.
- Familiar with telecommunications domain knowledge for determining the test environment matrix. For instance, for a video conferencing application, then the network, SIM card, and phone network capabilities play a big part in the test platform matrix.
- Familiar with the general telephony functions and their relationship (e.g. SMS, WAP, GSM). For example, incoming, dial, rejected, and answered states. With this knowledge and their interaction with the other telephone functions, test cases with state transition test methods can be designed properly.