"Reprint" Mobile Test flow

1. UI Test

The app's primary core UI is consistent with the actual design, and the interaction issues suggest that it can be confirmed with the product manager before the development implementation changes or optimizations are made.

2. App function test

According to the software description or user requirements to verify the implementation of the various functions of the app, the actual test process is generally based on functional test cases to execute. Test coverage is basically a test case-led, that is, in the functional testing section, is to verify that the test case is valid and complete, but also lead to another problem, the test case how to write the problem, another article to separate the test case to write the method.

3. Interrupt Testing

Simulate the user's actual use of the app is the interruption of the situation to test. such as: network disconnection, switch networks, power outages, call/SMS, listen to music, switch to other apps, open other app notifications, etc.

4. compatibility testing

New and older versions of compatibility testing at the functional, logical level, the same app running in different system versions, and adaptation testing between different models
Compatibility test: The compatibility test of the interface ensures that most of the functions are complete, and the app is guaranteed to run on different system versions.
Compatibility: screen, system version, etc. (the number of system bits must be considered)
This section is done through a third-party cloud platform

5. Performance testing,

Testable aspects
1. Installation and start-up time;
2.CPU occupancy;
3. Memory consumption;
4. Consumption of traffic;
5. Consumption of electricity;
6. Backend, test the application of various types of operations to meet user response time requirements, mainly testing points in the speed, 2g,3g,wifi, 4g must be covered to
7. The backend has network concurrency

6. Stability test, pressure test

1. Verify that the app responds correctly at various boundary pressures (e.g. battery, storage, speed, etc.)
2. The system resources are not used abnormally under the repeated/long-term operation; Android uses the ADB command
3. Stress testing is mainly focused on the back end, the front-end pressure test is currently measured less

7. Safety Testing

App security testing is roughly divided into the following categories:
1) Evaluate the security features of the app based on the corresponding security standards/industry standards, from the local storage of data to the transmission, processing and remote access of the data;
2) draw on some successful experiences in web app and network security testing to cut or adapt in the Smart Terminal app test;
3) Detection of user authorization level, data leakage, unauthorized access to the app;
4) Check the application's input validity, authentication, authorization, sensitive data storage, data encryption and so on, in order to detect potential security problems;
5) See if the app meets the requirements based on a variety of communication protocols or the appropriate industry security standards.

8. User Experience Testing

This simple is to stand on the user's point of view to use the app, learning low cost, easy to start and so on, can be user blind test, based on feedback from users to modify. Testers can compare with other competitors, or according to the interaction habits of larger vendor apps.

9. Regression testing-General This section recommends the use of automated testing, if there is no automated test, can be based on several aspects of testing

1. Function confirmation according to the product instruction or function document
2. Re-execute the test case with the main priority higher
3. Re-verify the bug

10. On-Line testing

Online testing is the product must be completed after the launch, this part can be based on the scenario of regression testing, where the network environment to cover all over

"Reprint" Mobile Test flow