Experience summary of mobile application software testing

with the progress of science and technology, mobile phone models are constantly changing, the function is more and more abundant. Correspondingly, more and more mobile phone application software is accompanied by the diversification of mobile phone function. In the face of a variety of mobile phone application software, how to test, testing and need to focus on what? This document is shared by test engineers in the domestic professional mobile application testing cloud service Platform ,www.ineice.com.

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, Function module test: First of all, the functional modules should be analyzed to test whether each function item can achieve the corresponding function. Basic functional testing is usually done based on the test caseor the process of the software itself (relatively simple, the fault is easier to find and solve).

2. Cross-event testing: Also known as event or conflict testing, 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 during the operation of the Plug and unplug the 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 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 the other storage area is erased, in order to There is a problem with the UI (for example, other features are not working properly and an exception occurs).

● boundary Pressure: Boundary processing has always been the easiest place for programmers to overlook.

● Responsiveness Stress: 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: The function of large data traffic, and then other functions, so that the network traffic is always in a very high state (such as video calls and other functions such as text messaging), verify that the function is still working properly, whether there is a network traffic bottleneck caused by a function exception.

Manual tests for stress tests can be very cumbersome and can be considered for automated testing. Unfortunately, there is no much-used tool, typically a tool developed by a developer, or a script written by an advanced tester.

4, capacity testing: that is, storage space is full of testing, including mobile phone users available memory and SIM card All the space is fully used test. 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 testing: That is, different brands, models of mobile phones (for the current product, mainly for different brands, models of mobile phone testing), different networks, different brands and different capacity of the SIM card compatibility between the test. 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. Usability / User Experience Testing: Easeof Use (useability)/ user experience refers to the ability to understand, learn, use and engage users when used under specified conditions, which is the adaptability of the interaction, A concentrated embodiment of functionality and effectiveness.

Experience summary of mobile application software testing