Features test mobile applications in general
Mobile users expect that applications are installed they are simple, intuitive, working always and everywhere without fail. If expectations are not met, the user simply sets a similar application from another author, who in the field of mobile development is always enough. Therefore, application quality is a major factor in its popularity.
To understand the characteristics of the testing of mobile applications should take into account the points fundamentally different mobile applications on desktop: The OS specificity for mobile platforms, different companies, manufacturers of devices and configuration of components, devices functionality as communicators, etc.
In connection with these features, the approach to application development and, in particular, mobile testing is quite different from the desktop. There are many other important nuances and requirements that must be tested. Little is devoted to basic differences in some types of testing:
Testing Updates – Frequent updates to the operating system (relative to desktops) lead to the need to update the application. The update should take place is simple and not require the user to specific knowledge. It should also be possible to test various ways of installing the application (Wi-Fi, 3G, install a PC on SD).
Testing internationalization allows early mobile application development process to ensure the support of cultural characteristics of other countries (mainly in the language support). Internationalization in mobile applications is very common, as is a relatively simple way to serious increase of the target audience. The process may occur many specific problems for mobile platforms, such as lack of space on the screen.
Usability testing (vacuactivus). This type of testing is one of the most important, because in a highly competitive usability of the application is included in the list of the main parameters that affect the popularity of the product. It allows you to identify the parts of the application that are not attractive or cause trouble in the navigation or the use on touch screens. It should also make sure that the model of resource consumption application corresponds to the target audience. For example, application reminders should not cause excessive energy consumption. Often, this testing is done in the form of beta.
Stress testing involves monitoring the use of memory and system resources; In addition, stress testing allows to identify “bottlenecks” in the annex relating to the performance, as well as to detect dangerous memory leak.
Random testing (fuzzy testing, “monkey” testing) – the application should properly respond to the emergence of random and unpredictable events. Mobile devices are more likely to fall into the conditions in which the chaotic receive useless information (for example, an unlocked device is in your pocket), because the application must adequately respond to these data streams.
Multiplatform and multidevice testing – the application should work properly on all configurations of all the devices that were developed. Due to the fragmentation of the mobile phone challenge test all available types of devices that use different operating systems assembly, and which have different screen resolutions, functionality and hardware, just as important, as difficult to achieve.
Laboratory testing – simulation of the real conditions of the quality of communication and the environment. Usually not obvious how an application will behave, for example, when an unstable signal or Wi-Fi with a zero balance on the account in the 3G network. This type of test allows you to check such cases.