Software Test model

Many development models are introduced in software engineering, such as waterfall model, prototype model, spiral model and so on, and the more popular RUP, these models have good guidance to the software development process. However, in the software engineering does not give sufficient attention to testing, software testing and development is closely related to a series of planned activities, so software testing also requires the corresponding test model to guide. Here is a brief introduction to some of the test models

1.V Models

The V-model is the most representative model of software testing, which was first proposed by Paul Rook in the 1980s to improve the efficiency and effectiveness of software development. V-model is a variant of the software development waterfall model, reflecting the relationship between the test activity and the analysis and design, which clearly shows 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. The left-hand side of the development process, which corresponds to the various stages of the test process, rises to the right.

Each stage features:

V-model software testing, including bottom-level and high-layer testing. The underlying test is for the correctness of the source code, high-level testing is to enable the entire system to meet the needs of users.

Unit tests: Code-based testing that is initially performed by the developer to verify that the parts of its executable code have met the expected functional requirements

Integration testing: Verify that the integration between 2 or more cells is correct, and that the interfaces between the elements defined in the detailed design are examined in a targeted manner

System test: Verify the System design, start to simulate the operation of the system with the customer environment, to verify whether the system has achieved the function and performance defined in the outline design.

Confirm Test and acceptance testing: tested by testers, business experts or users, and traced to the software requirements specification for testing to determine whether the software implementation meets user requirements or contract requirements.

Limitations:

It only takes the test process as a stage after the requirement analysis, outline design, detailed design and coding. Easy to understand as testing is the last phase of software development, mainly for the program to test the search for errors, and the requirements of the analysis phase hidden problems only in the late acceptance test can be found. (The limitation of the V model is that there is no clear indication of early testing and that the principle of "early and continuous software testing" cannot be demonstrated)

2.W Models

The W model is proposed by Evolutif company, and the W model increases the verification and validation activities synchronously during each phase of software development, relative to the V model. The W model consists of two V-shaped models representing the test and development process, which clearly shows the parallel relationship between test and development. It can be said that the V model of natural development, it emphasizes the test along with the entire software development cycle, and the test object is not only the program, requirements, functions and design nursery rhymes to test, and as long as the corresponding development activities are completed, the test activity can be started, can also say that testing and development synchronization, so as to facilitate early detection of problems

According to the requirements of the W model, once the documentation is provided, the test conditions must be determined in time and the test case written. When requirements are submitted, you need to identify high-level test cases to test these requirements. When the summary design is complete, you need to determine the test conditions to find the design flaws in the phase.

Limitations:

Both the W model and the V Model regard software development as a series of serial activities such as requirements, design, and coding. Software development and testing maintain a linear relationship, requiring strict instructions to indicate that the previous phase is completely closed before the next phase can be formally started. This makes it impossible to support iterative development and change adjustments, and the W model simply cannot relieve the challenges of test management for many documents that require post-mortem or no documentation.

3.H Models

The H model completely independent of the test activity, creating a completely independent process that clearly reflects test readiness activities and test execution activities. The H model reveals a principle: software testing is a separate process that runs through the entire life cycle of the product, and in parallel with other processes. The H model indicates that software testing should be prepared early and executed as early as possible.

The H model reveals that different test activities can be carried out in a sequential order, but may also be iterative, as long as a test is ready to go, and the test execution activity can be carried out.

Summary:

Software testing is a process used to promote the correctness, completeness, security and quality of the software, which is an essential part of software development. Test models, like software development models, are constantly evolving, improving, and becoming more flexible and easy to use.

Software Test model