Turn: Mobile application Software Test summary

For the product of the mobile phone project (application software), mainly for the system testing. For system testing of mobile application software, we usually carry out the following aspects: Functional module Testing, cross-event testing, stress testing, capacity testing, compatibility testing, usability/user experience testing, etc.

1, functional module test: first analyze the function of the functional module, test each function item can achieve the corresponding function. Generally, depending on the test case or the process of the software itself, you can complete the basic Functional testing (relatively simple, fault is easier to find and resolve).

2, cross-event testing: also called an event or conflict test, which is a test in which a feature is executing while another event or operation interferes with the process. For example, during a call to receive SMS Or alarm triggering, the application software operation process Plug and unplug charger. Conflicting events that perform interference do not cause serious problems such as application exceptions, phone freezes, or huaping. In addition, we need to pay attention to the priority level of each cross-event, and check whether the system can be processed according to the priority of each event. It is not possible to hang a lower priority event because of a high priority event.

cross-event testing is very important, and it is common to find some potential problems in the application software. In addition, the Chinese and English mode switch mobile phone should pay attention to the Chinese and English mode after switching the function of the implementation of the problem (this is mainly for mobile phone application Support language adaptive function), which is usually ignored by testers.

　　3, Pressure test: also called boundary value tolerance test or limit load test. That is, during the testing process, the maximum capacity, boundary value or maximum load limit of a certain software function is reached, and it is still related to operation. For example, continuous SMS receiving and sending, more than the Inbox and SIM card can store the maximum number of bars, still carry out the receipt or transmission of short messages, so as to detect the performance of the software in the ultra-normal conditions, and then evaluate the user can accept.

The types of stress tests that can be applied to a mobile phone include:

Storage pressure: Because the mobile phone uses a stack of storage, so when a storage block is full, if the programmer does not do the appropriate processing or processing is not good, it is easy to cause other storage areas to be erased, resulting in a problem on the UI (such as other functions can not be used properly, an exception occurs).

Boundary pressure: Boundary processing has always been the easiest place for programmers to overlook.

responsiveness: Sometimes an operation can take a long time, and if the tester continues to perform other operations during processing, it is prone to problems.

network traffic pressure: Perform the functions of large data traffic, and then perform other functions, So that the network traffic is always in a very high state (such as video calls and other functions such as SMS), to verify that the function can still be normal working , if there is a feature exception due to network traffic bottlenecks.

The pressure test with manual testing may be very complex lock, you can consider automated test . Unfortunately, there is no much-used tool, typically a tool developed by a developer, or a script written by an advanced tester.

4, volume test: that is, the test when the storage space is full, including the memory available to the mobile user and all the space of the SIM card is fully used. At this time, the editable module and storage space for any operational testing, if the software in the limit capacity of the process is not good, it may lead to the death or serious huaping problems such as the appearance.

5, Compatibility test: that is, different brands, models of mobile phones (for the current products, mainly for different brands, models of mobile phone testing), different networks, Compatible testing between different brands and SIM cards of different capacity sizes. Take the short message as an example: China Telecom's PHS received from China Mobile or Chinese Unicom GSM sent short message, need to verify the display and reply function is normal and so on. For example, the application software in the Nokia N80, N93 mobile phone running, whether all functions can be normal use, the interface is displayed normal and so on.

6, Ease of use/user experience Testing: Ease of Use (useability)/user experience refers to the ability of software products to be understood, learned, used and attracted to users when used under specified conditions, is the adaptability of the interaction, A concentrated embodiment of functionality and effectiveness.

Ease of use is the most basic and important requirement for terminal software (which is the interactive software). Bad software is hard to attract users, let alone improve user loyalty to the software. Ease of use embodied in: WYSIWYG, a use of knowledge, a learning will be, convenient and quick to complete the expected function. Easy-to-use software allows a new user to learn quickly, using our software, and in the process of using software to reflect our intimate service, beyond the expectations of users is the embodiment of our pursuit of the goal.

Turn: Mobile application Software Test summary