confirmation test
1. Confirm whether the software design complies with the software requirements, and whether each requirement of the software can be traced to the software design.
2. Confirm the state sequence and state change (Functional Block Diagram).
3. Verify that data and control flow meets security, functionality , and performance requirements.
4. Confirm the functionality of the software, the consistency of hardware, software and user interface, performance criteria, whether the configuration data meets the specified configuration management procedures, whether the logic, calculation and interface accuracy meet the requirements of the system environment.
5. Confirm the version of the software to be tested, which must be the software after passing the module test and integration test.
6. The configuration script required for testing needs to be consistent with the software source code version.
The confirmation test can verify the software engineering project according to the development requirements documents and other materials provided by the client of the software product , and check whether the software product structure meets the test running speed and concurrent number of different types of software products under test on various special test equipment. , Internal organizational structure, component categories and responsibilities, interface specifications, interaction methods, component development methods, software extensions and modifications, and other high-quality development requirements meet the requirements of the development documents.
There are two possibilities for the results of the confirmation test, one is that the function and performance indicators meet the requirements of the software requirements specification, and the user can accept it; the other is that the software does not meet the requirements of the software requirements specification, and the user cannot accept it. Serious errors and deviations are found only at this stage of the project, and it is generally difficult to correct within the scheduled construction period. Therefore, it is necessary to negotiate with the user to find a proper solution to the problem. Form the "Software Product Confirmation Test Report" according to the test results.
Significance of confirmation testing for software companies:
The "Software Confirmation Test Report" issued after the confirmation test can be used as the technical appraisal basis for the declaration of national, provincial and municipal scientific and technological achievement awards, and the "Small and Medium-sized Enterprise Innovation", "Science and Technology Project Acceptance", "Science and Technology Achievement Appraisal", " Independent Innovation Product Identification" and other powerful proofs.
Tags: validation testing, product testing
Source of the article: Seven Principles of Software Validation Testing-Help you perform QA testing better- Chengdu Kexin Youchuang Information Technology Service Co., Ltd.