Software Test Summary (IV)

 

After learning the unit test and integration test, the assembly test has been completed. The next step is the validation test. This section describes the validation test. A validation test, also known as a validity test or a qualification test, is used to verify whether the features of the system, such as performance, meet the specifications required. For example:

Effectiveness testing and software configuration review are two of the most important tasks of validation testing.

Verify that the testing is generally performed in a simulated environment or in a development environment using the black box testing method. Verify that the software functions and features are consistent with the user's requirements according to the requirement specification. After validation testing, there may be two situations:

1. The functions, performance, and other requirements of the software have been met and may be considered qualified software.
2. Find a large deviation between the software and the requirement specification and obtain a list of defects. The workload for such errors is very large, and it is often difficult to fix the defects found before the delivery period. In this case, the Development Department and the user need to negotiate and solve the problem.

 

Software Configuration review, also known as configuration audit, refers to all information items generated during the software engineering process: documents, reports,Program, Tables, data, etc. In this phase, we will mainly review the completeness of SCI, check the integrity and correctness of all documents of the software, repair the defects found, and arrange the directories so that the maintenance can proceed smoothly.

 

The validation test is carried out following the integration test to verify that the assembled procedure meets the requirement specification. The validation test is the last development activity organized by the software development unit. After the test is completed, the software is delivered for acceptance. Therefore, the Development Unit must pay great attention to this work, just like the integration test, the independent test team should also be responsible for implementation.

 

Okay, this section ends. The next section describes the fourth step of hierarchical testing-system testing. Thank you!