App complete test process

Time:2022-5-17

Test process

  • The first is the confirmation and preparation of test resources
  • Design and review of test cases
  • Smoke testing
  • functional testing
  • UI test (after all, you can only see the UI with data)
  • Interruption test (network disconnection, network switching, power failure, incoming call / SMS, listening to music, switching to other apps, opening notifications of other apps, etc.)
  • Compatibility and adaptation test
  • performance testing
  • Stability test
  • Test analysis and test report output

detailed description

UI test 1

Whether the main core UI of the app is consistent with the actual design renderings; Problems and suggestions on interaction can be confirmed with the product manager first, and then the development can be changed or optimized

2. Function test

Verify the realization of each function of the app according to the software description or user requirements. The actual test process is generally performed according to the function test cases. Test coverage is basically dominated by test cases, that is, in the functional test part, it is to check whether the test cases are effective and complete, which leads to another problem, how to write the test cases.

3. Interrupt test

Simulate the interruption that users will encounter when using the app in real life For example: network disconnection, network switching, power failure, calling / SMS, listening to music, switching to other apps, opening notifications of other apps, etc

4. Compatibility and adaptation test

Compatibility test of the old and new versions at the functional and logical levels, the same app running in different system versions, and the adaptation test between different models. Compatibility test: the compatibility test of the interface can ensure the perfection of most functions; App ensures running adaptability on different system versions: screen, system version, etc. (the number of system digits must be considered). This part is carried out through a third-party cloud platform

5. Performance test

Testable aspects – installation and startup time – CPU occupation – memory occupation – traffic consumption – power consumption – back end, test whether various operations in the app meet the user response time requirements, mainly in terms of network speed, 2G, 3G, WiFi and 4G must be covered – there is network concurrency at the back end

6. Stability test and pressure test

Under various boundary pressure conditions (such as battery, storage, network speed, etc.), verify whether the app can respond correctly
Whether the system resources are occupied abnormally under repeated / long-term operation; Android uses the ADB command
The stress test is mainly focused on the back end, and the front-end stress test is less at present

7. Safety test

App security testing can be roughly divided into the following categories:
Evaluate the security characteristics 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 data;
Learn from some successful experiences in web app and network security testing, and cut or adapt in intelligent terminal app testing;
Detect the user authorization level, data leakage, illegal authorized access, etc. of the app;
Check the input validity verification, authentication, authorization, sensitive data storage, data encryption and other aspects of the app in order to find potential security problems;
Check whether the app meets the corresponding requirements based on various communication protocols or corresponding industry security standards.

8. User experience test

This is simply to use the app from the perspective of users. It has low learning cost and is easy to use. Users can conduct blind testing and modify it according to the feedback of users. Testers can compare with other competitors or according to the interaction habits of larger manufacturers’ apps.

9. Regression test

Generally, automated testing is recommended in this part. If there is no automated testing, it can be tested according to the following aspects:

  • Confirm the function according to the product manual or function document
  • Re execute the test cases with higher priority
  • Revalidate bug
10. Online test

Online testing must be completed after the product goes online. This part can be regression tested according to the scenario, in which the network environment should be fully covered

Recommended Today

Android studio signature packaging APK tutorial

When APK is released to the application market, it needs to upload the release version APK with key signature. Here are two methods of packaging signature APK. 1. Generate signature file Method for Android studio to generate signature file 2. Generate APK file Tool signature packaging1) Select generate signed bundle / APK… In the build […]