V model 1. The V model
contains both high-level testing (in order to make the entire system meet the needs of users) and low-level testing (for the correctness of source code);
2. Unit and integration are to verify the program design and whether the execution program meets the software design Requirements;
3. Confirmation and acceptance testing, trace back the requirements specification, confirm whether the software meets user needs or contract requirements;
W model
It emphasizes: testing accompanies the entire software development cycle, the object of testing is not only the program, but also the requirements, functions, and design Testing; testing and development are synchronized, which helps to find problems as early as possible. For example, the requirements can be tested as soon as they are completed.
H model
In this model, the software testing model is an independent process that runs through the entire product cycle and runs concurrently with other processes.
The X model
positions exploratory testing, which is to carry out special types of testing that are not planned.
Pre-test model
The agile testing model
emphasizes testing the system from the user's perspective, focusing on continuously iterative testing of newly developed functions, and it is recommended to start testing as soon as possible.
