Software Testing Process Model

(1) v MODEL

The V model is a variant of the waterfall model for software development. It reflects the relationship between test activities and analysis and design. It describes the basic development process and test behavior from left to right, it clearly shows the different levels in the test process, and clearly describes the mappings between these test phases and various stages during the development process:

The V model has certain limitations. It only takes the test process as a stage after requirement analysis, outline design, detailed design, and coding, problems hidden in the demand analysis phase will not be detected until the acceptance test is conducted later.

(2) W Model

In the V model, the tests that should be performed simultaneously at various stages of software development are added and evolved into a W model, because the development is actually "V", and the tests are also "V" in parallel with this ":

W model regards software development as a series of serial activities such as demand, design, and coding. Software Development and testing maintain a linear relationship between front and back. Strict instructions are required to indicate the end of the previous stage, to officially start the next stage. In this way, iteration and change adjustment are not supported.

(3) h Model

It completely isolates test activities and forms a completely independent process. It clearly shows test preparation activities and test execution activities:

In the H model, software testing is an independent process that runs throughout the entire product cycle and is executed concurrently with other processes. When a test time point is ready, the software test enters the test execution stage from the test preparation stage.

(4) x Model

The left side of the X model describes the code and tests for separate program fragments. After that, the code is frequently handed over and integrated into executable programs. In addition, these executable programs also need to be tested. Finished Products that have passed the integration test can be sealed and submitted to the user. They can also be part of the larger scale and scope inheritance:

(5) pre-test model

It is a model that closely integrates testing and development:

The pre-test model integrates the test and Development lifecycles. Each delivered development result must be tested in a certain way. Test plan and design are carried out in the test phase, and test and development are combined to ensure the independence of Acceptance Test and technical test.

 

 

 

 

 

Software Testing Process Model