Software testing methods based on software testing

There are several methods of software testing.

1. According to whether to view the internal structure of the program, it is divided into:

(1) Black-box testing (black-box testing): only care about the results of the input and output dao.

(2) White-box testing (white-box testing): To study the source code and program structure inside.

2. According to whether the program is running or not, it is divided into:

(1) Static testing (static testing): refers to the process of not actually running the software under test, but only statically checking the possible errors in the program code, interface or documentation.

(5) Dynamic testing refers to the process of actually running the program under test, inputting the corresponding test data, and checking whether the output results are consistent with the expected results.

3. Divided by stage:

(1) Unit testing refers to checking and verifying the smallest testable unit in the software.

(2) Integration testing is the next stage of unit testing, which refers to assembling the unit modules that pass the test into a system or subsystem, and then testing, focusing on testing the interface departments of different modules.

(3) System testing refers to testing the entire software system as a whole, including testing functions, performance, and the hardware and software environment in which the software runs.

(4) Acceptance testing (acceptance testing) refers to user testing in the later stage of system testing, or testing with the participation of quality assurance personnel such as testers. It is also the last process for the software to be officially handed over to users. .

4. Black box testing is divided into functional testing and performance testing:

(1) Function testing is an aspect of black box testing, which checks whether the actual software functions meet the needs of users.

(2) Performance testing (performance testing), software performance testing is divided into:

General performance test: refers to the performance test that allows the system under test to run in a normal software and hardware environment without imposing any pressure on it.

Stability testing is also called reliability testing (reliability testing): it refers to the continuous operation of the system under test to check the stability of the system during operation.

Load testing (load testing): It refers to allowing the system under test to run continuously within the limit range of its tolerable pressure to test the stability of the system.

Stress testing (stress testing): refers to continuously increasing the pressure on the system under test until the system under test is crushed to test the maximum pressure that the system can withstand.

5. Other test types:

Regression testing (regression testing) refers to the use case of repeating the test of the previous version when testing the new version of the software.

Smoke testing (smoke testing) refers to verifying whether the basic functions of the software are implemented and whether they are testable before conducting large-scale testing on a new version.

Random testing means that all input data in the test is randomly generated, and its purpose is to simulate the real operation of the user and find some marginal errors.

Mobile test series of software testing

 Software testing full stack series

Guess you like

Origin blog.csdn.net/m0_37449634/article/details/131580867