Performance, compatibility, interface, cross-testing of mobile APP test points

I have written the main points of APP functional testing and security testing before, and today I am sharing some of them, including performance testing, compatibility testing, excuse testing, and cross-testing.

Performance test: evaluate the time and space characteristics of the app;

limit test: verify whether the app can respond correctly under various boundary pressure conditions, such as battery, storage, network speed, etc. Including: install the app when the memory is full, power off the phone when running the app, and disconnect the network when running the app.

Response ability test: Test whether various operations in the app meet the user's response time requirements. Including: the response time of app installation and uninstallation, and the impact time of various functional operations of the app.

Stress test: whether the system resources are abnormally occupied under repeated/long-term operations. Including: repeatedly install and uninstall the app, check whether the system resources are normal, and repeatedly operate other functions to check whether the system resources are normal.

Performance evaluation: Evaluate the usage of system resources in typical user application scenarios.

Capacity test: that is, the test when the storage space is full, including the test in which the available memory of the mobile phone user and all the space of the SIM card are used. At this time, perform any operation test related to the storage space on the editable module. If the software is not handled well under the limit capacity state, it may cause problems such as crash or serious blurred screen.

Compatibility test: that is, the compatibility test between different system frameworks, different brands, models, and resolutions of mobile phones that do not vomit that network, and SIM cards of different sizes.
Specifically include:
1. Whether it is compatible with local and mainstream apps
2. Based on the difference between the development environment and the production environment, check that the App is connected under various network connections (WiFi, GSM, GPRS, EDGE, WCDMA, CDMA1x, CDMA2000, HSPDA, etc.). Whether the data and application are correct
3. Whether it is compatible with various devices, if there is cross-system support, it is necessary to check whether various behaviors are consistent under each system
4. Compatibility of different operating systems, whether it fits
5. Compatibility of different mobile phone screen resolutions
6. Compatibility of different mobile phone brands

Interface test: The server generally provides data in JSON format to the client, so we are serving The client needs to perform interface testing to ensure that the interface provided by the server and the converted JSON content are correct, and that there are corresponding return values ​​for branches and exception flows. This block test can be tested using the itest framework. The most convenient is to use httpclient for interface testing.

Cross-event testing: Also called event conflict testing in APP testing , it means that a function is in the process of being executed, while another event or operation interferes with the process. For example, the interaction test between the App and key applications such as incoming calls, file ixaz, and music listening when the App is running in the front/background state, etc.

Including:
whether multiple apps running at the same time affect normal functions.
Whether the front/background switching of the app will affect normal functions.
Make/receive calls while the app is running.
Send/receive information while the app is running.
Send/receive emails while the app is running.
Switch the network (2G/3G/WIFI) when the App is running.
The App is running to browse the web.
Bluetooth is used to transmit/receive data while the app is running.
When the app runs, use the camera, calculator, and mobile phone's own device.
Plug and unplug the charger while the app is running.

Conflict events of execution interference cannot cause serious problems such as abnormal software applications, mobile phone freezes, or blurry screens. It is also necessary to pay attention to the priority levels of each cross-event, and check whether the system can handle the events in sequence according to the priority level of each event. A lower priority event cannot hang due to execution of a higher priority event. In addition, mobile phones with Chinese and English mode switching should pay attention to the problems existing in the function realization after the Chinese and English modes are switched.