Software Testing Classification Description Notes
1. Performance test
Performance testing is testing to obtain or verify system performance indicators. In most cases, performance tests are performed under different load conditions.
2. Load testing
Load testing is to discover the performance problems existing in the system by changing the system load mode, increasing the load, etc. In order to find problems in the software system, including performance bottlenecks, memory leaks, etc.
3. Stress test
Stress testing is divided into long-term stability stress testing under high load and destructive stress testing that leads to system collapse under extreme load conditions. Mainly to determine system stability.
(You can find memory leak problems and problems affecting system stability faster)
4. Recovery test
Mainly check the fault tolerance of the system. Use various methods to force the system to fail, then verify that the system can recover and restart the system as soon as possible within the specified time interval.
5. Usability testing
It is highly subjective to test whether the software is easy to use. Generally, it is necessary to evaluate the ease of use according to the test feedback information of many users.
6. Regression testing
Refers to the retest after the error is corrected or the software function and environment are changed to confirm that the modified part will not affect other functions.
7.Alpha test
A kind of early user test, the company organizes employees and some users internally, and conducts acceptance tests under the simulated actual operating environment.
8. Beta testing
A post-user test, the system has passed internal testing, most bugs have been fixed, and will be released soon. Release the version in one or more real environments and test it.
9. Smoke test
Use a small number of experienced people to test whether the main functions and main business processes of the entire system are implemented and stable in a relatively short period of time.
10. Integration Testing
Integration testing is also called assembly testing or joint testing. On the basis of unit testing, all modules are assembled into subsystems or systems according to design requirements (eg, according to the structure diagram) for integration testing.
11. Black Box Testing
Black box testing is to treat the test object as a black box. The tester does not consider the internal logical structure and internal characteristics of the program at all, and only checks whether the function of the program is based on the requirements specification of the program.
conforms to its functional description.
1) Equivalence class division method 2) Boundary value analysis method 3) Cause and effect diagram method 4) Decision table method 5) Error inference method 6) Scenario method
12. White box testing
White-box testing is a careful examination of the procedural details of the software. Think of the test object as an open box that allows the tester to use the program's internal logical structure and related information to design or select
Test cases are used to test all logical paths of the program. Determine whether the actual state matches the expected state by examining the program state at various points.
1) Static analysis method: The technique of testing without running is to check whether the representation and description of the software are consistent, without ambiguity, and without conflict.
2) Dynamic analysis method: It is the analysis of software system behavior before, during and after the software runs in a simulated or real environment. Dynamic analysis involves the use of specific
Expect the result to go into a formal run. It shows whether the system is correct or incorrect in the checked state. The most important of the dynamic analysis techniques are path and branch testing.
The dynamic analysis method is further divided into: statement coverage, path coverage, conditional coverage, branch coverage, conditional and decision coverage, and combined coverage.