Software Test model

Four classic models

First, the introduction of the model

(1) v-model

The process from left to right in the V model describes the basic development process and test behavior. The value of the V model is that it clearly identifies the different levels that exist in the testing process and clearly describes the correspondence between these test phases and the stages during the development process. Limitations: The test as the last activity after coding, requirements analysis and other pre-production errors until the late acceptance test can be found.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/5A/66/wKioL1T9NJOQ3kJdAADXOusi_48503.jpg "title=" V model. jpg "alt=" wkiol1t9njoq3kjdaadxousi_48503.jpg "/>

(2) W Model

W Model is more scientific than V model and W model. The W model is the development of the V model, emphasizing that testing is accompanied by the entire software development cycle, and that the object of testing is not just the program, but also the requirements, functions and design. Testing and development are carried out synchronously, which facilitates the early detection of problems.

The W model also has limitations. Both the W model and the V Model regard software development as a series of serial activities such as requirements, design, and coding, which cannot support iteration, spontaneity, and change adjustment.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5A/6A/wKiom1T9NRrTJ1LVAADVjqRnmNA622.jpg "title=" W model. jpg "alt=" wkiom1t9nrrtj1lvaadvjqrnmna622.jpg "/>

(3) x model

The left side of the X model describes the separate coding and testing for individual program fragments, which are then frequently handed over and then tested by integration into the executable program. Finished products that have been tested for integration can be encapsulated and submitted to the user, or as part of a larger scale and in-scope integration. Multiple parallel curves indicate that changes can occur in various parts. As can be seen in the diagram, the X model also locates exploratory tests, which are special types of tests that are not planned beforehand, which often help experienced testers to discover more software errors outside of the test plan. But this may result in the human, material and financial waste of the test, the proficiency of the testers is more demanding.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/5A/66/wKioL1T9NtDQUXDPAAF0G2UmKws724.jpg "title=" x model. jpg "width=" 628 "height=" 445 "border=" 0 "hspace=" 0 "vspace=" 0 "style=" width:628px;height:445px; "alt=" Wkiol1t9ntdquxdpaaf0g2umkws724.jpg "/>

(4) H model

h model, the software test process activities are completely independent, throughout the product cycle, and other processes in parallel, when a test point is ready, you can from the test preparation phase to the test execution phase. Software testing can be done as early as possible, and can be carried out hierarchically depending on the object being measured.

This demonstrates a test "microcirculation" at a certain level throughout the production cycle. Other processes marked in the diagram can be any development process, such as the design process or the coding process. That is, as long as the test conditions are ripe and the test preparation is completed, the test execution activity is ready.

The H model reveals a principle: software testing is a separate process that runs through the product Life cycle , and in parallel with other processes. The H model indicates that software testing should be prepared early and executed as early as possible. Different test activities can be carried out in a sequential order, but may also be repeated, as long as a test is ready to go, the test execution activity can be carried out.

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/5A/66/wKioL1T9N5Wws_LHAACQRZue_wc817.jpg "title=" h.jpg " alt= "Wkiol1t9n5wws_lhaacqrzue_wc817.jpg"/>

Ii. Characteristics of the model

V-Model – very clearly marks the different types of tests that exist during the testing process.

W Model--the correspondence between development and testing in the production cycle is clearly marked.

The X-model-this model indicates that the entire test process is being explored.

H-Model-software testing is a separate process that runs through the entire life cycle of the product and in parallel with other processes.

This article is from the "Sailing" blog, please be sure to keep this source http://yancaiqihang.blog.51cto.com/4626067/1618561

Software Test model