Several simple software test models

Software Testing is one of the important means of software quality assurance, and software testing model is the working framework of software testing, which is used to instruct software testing process. Today, we present a few basic software testing models-V-model, W-model, and pre-test model.

A, V-model:

in the process of traditional waterfall software development, the test process is only used as a stage after requirement analysis, summary design, detailed design and coding, and no further description is made on the software testing process. The V-model complements the software testing process for the waterfall model. The V-model was first proposed by the late Paul Rook in the late 80. In this model, the test process is added to the second half of the development process, as shown in.

On the development side, start by defining the business requirements, then converting the requirements to software specifications, then to the profile design and the detailed design, and finally coding into the program code. On one side of the test execution phase, unit tests are followed by integration tests, system tests, and finally acceptance tests, which form different levels (levels) of software testing and correspond to the corresponding stages of the development process.

Two, W Model:
Errors can occur at all stages of the software development process. According to the statistics of some large-scale software systems abroad, the demand analysis and design phase generated errors accounted for 64%, coding errors accounted for 36%. Software errors are transitive, that is, if the errors produced by the requirements analysis are not found, they are passed to the design and coding in turn. The discovery and resolution of software errors is amplified. It is estimated that errors generated during the analysis design phase, if the test process after the end of the code is discovered, is about 10 times times the cost of finding and resolving errors in the analysis design phase. If the error is discovered and resolved after the product is delivered, it will cost more than 100 times times. As a result, the sooner the test is done, the less the cost of finding and fixing the error, the less the risk. According to this view, Systeme Evolutif, based on the V-model, proposes a W-model, as shown in.

In the diagram, the W-model is overlapped by two "V". One "V" represents the development process, including requirements analysis, specification generation, software design, code programming, software construction, system construction, and installation phases. Another "V" represents the test process, including requirements testing, specification testing, design testing, unit testing, integration testing, system testing, and acceptance testing activities. Each test activity of software testing corresponds to each stage of the development process.

Third, the pre-test model:

A pre-test is a model that closely integrates testing and development, such as.

The pre-test model integrates the life cycle of development and testing, identifying key activities from the start to the end of the project life cycle. If some of these activities are not well executed, the likelihood of project success will be reduced.

Several simple software test models