The App mainly checks whether the UI is consistent with the actual design renderings; for suggestions on interaction issues, you can first confirm with the product manager. After the confirmation is passed, the development can start to implement changes or optimizations
2.App function test
Verify the implementation of each function of the App based on the software description or user requirements. The actual testing process is generally performed based on functional test cases. Test coverage is basically dominated by test cases, which means that in the functional testing part, it is to check whether the test cases are valid and complete, which leads to another problem, how to write test cases, which will be covered in another article Describe how to write test cases separately.
Compatibility testing of old and new versions at the functional and logical levels, the same App running on different system versions, and adaptation testing between different models Compatibility testing: Interface compatibility testing can ensure that most functions are perfect; App Guaranteed to run on different system versions Adaptability: screen, system version, etc. (system digits must be considered)
1. Under various boundary pressure conditions (such as battery, storage, network speed, etc.), verify whether the App can respond correctly 2. Under repeated/long-term operations, whether system resources are occupied abnormally; Android can use adb commands 3. Stress testing mainly focuses on the back-end, and there are currently fewer stress tests on the front-end
7. Security Test
App security testing is roughly divided into the following categories: 1) From local storage of data to data transmission, processing and remote access, evaluate the security features of the App based on corresponding security standards/industry standards; 2) Learn from Some successful experiences in Web App and network security testing are cut or adapted in smart terminal App testing; 3) Detect the user authorization level of the App, data leakage, illegal authorized access, etc.; 4) Validity of input to the App Detect verification, authentication, authorization, sensitive data storage, data encryption, etc., in order to discover potential security issues; 5) Check whether the App meets the corresponding requirements based on various communication protocols or corresponding industry security standards.
8. User experience testing
To put it simply, this means using the App from the user's perspective. It has low learning costs and is easy to use. It can be blindly tested by users and modified based on user feedback. Testers can compare with other competing products, or based on the interaction habits of larger manufacturers' apps.
Regression testing--Generally, it is recommended to use automated testing for this part. If there is no automated testing, you can test it in several aspects
1. Confirm the function according to the product manual or functional document
Re-execute the main test cases with higher priority 3. Re-verify the bug
Online test
Online testing must be completed after the product is launched. This part can be regression tested according to scenarios, and the network environment must be fully covered
Of course, when testing on the mobile terminal, you can use some automated testing tools, such as Appium, or find some third-party testing platforms. The better ones in China are testin, testbird, and abroad, testdroid, PerfectoMobile
UI Test
The App mainly checks whether the UI is consistent with the actual design renderings; for suggestions on interaction issues, you can first confirm with the product manager. After the confirmation is passed, the development can start to implement changes or optimizations
2.App function test
Verify the implementation of each function of the App based on the software description or user requirements. The actual testing process is generally performed based on functional test cases. Test coverage is basically dominated by test cases, which means that in the functional testing part, it is to check whether the test cases are valid and complete, which leads to another problem, how to write test cases, which will be covered in another article Describe how to write test cases separately.
Interrupt test
Compatibility Test
Compatibility testing of old and new versions at the functional and logical levels, the same App running on different system versions, and adaptation testing between different models
Compatibility testing: Interface compatibility testing can ensure that most functions are perfect; App Guaranteed to run on different system versions
Adaptability: screen, system version, etc. (system digits must be considered)
Performance testing,
Testable aspects
The backend has network concurrency
Stability test, stress test
1. Under various boundary pressure conditions (such as battery, storage, network speed, etc.), verify whether the App can respond correctly
2. Under repeated/long-term operations, whether system resources are occupied abnormally; Android can use adb commands
3. Stress testing mainly focuses on the back-end, and there are currently fewer stress tests on the front-end
7. Security Test
App security testing is roughly divided into the following categories:
1) From local storage of data to data transmission, processing and remote access, evaluate the security features of the App based on corresponding security standards/industry standards;
2) Learn from Some successful experiences in Web App and network security testing are cut or adapted in smart terminal App testing;
3) Detect the user authorization level of the App, data leakage, illegal authorized access, etc.;
4) Validity of input to the App Detect verification, authentication, authorization, sensitive data storage, data encryption, etc., in order to discover potential security issues;
5) Check whether the App meets the corresponding requirements based on various communication protocols or corresponding industry security standards.
8. User experience testing
To put it simply, this means using the App from the user's perspective. It has low learning costs and is easy to use. It can be blindly tested by users and modified based on user feedback. Testers can compare with other competing products, or based on the interaction habits of larger manufacturers' apps.
Regression testing--Generally, it is recommended to use automated testing for this part. If there is no automated testing, you can test it in several aspects
1. Confirm the function according to the product manual or functional document
Re-execute the main test cases with higher priority
3. Re-verify the bug
Online test
Online testing must be completed after the product is launched. This part can be regression tested according to scenarios, and the network environment must be fully covered
Of course, when testing on the mobile terminal, you can use some automated testing tools, such as Appium, or find some third-party testing platforms. The better ones in China are testin, testbird, and abroad, testdroid, PerfectoMobile