Confirm the basic method of the test
(This article is reproduced from Software Engineering Expert Network
Www.21cmm.com)
After the integrated test, the software has been completely assembled, and the interface errors have also been excluded, and the final step of the software test - confirming the test. Confirm that the test should be checked whether the software can work according to the contract requirements, that is, meet the confirmation standard in the software requirements instructions. 1. Confirm the test standard implementation software confirmation to test through a series of ink cartridges. Confirmation The test also needs to develop test plans and processes. The test plan should specify the types and test progress of the test. The test process defines some special test cases to explain whether the software is consistent with the demand. Nothing is still a process, it should focus on whether the software meets all the features and performances of the contract, whether the documentation is complete, accurate man-machine interface, and other aspects (for example, portability, compatibility, error recovery ability, maintenanceability Whether or not to satisfy users. There are two possibilities for confirmation tests. One is the requirements of functional and performance indicators to meet software requirements. The user can accept; the other is that software does not meet the requirements of software requirements, and users cannot accept. Projects By this stage, they have found that severe errors and deviations are generally difficult to correct within a predetermined period of time, so they must negotiate with the user to seek a way to properly solve the problem. 2. Another important part of configuring the review confirmation test is the configuration review. The purpose of review is to ensure that the software is fully equipped, classified or order, and includes the details necessary for software maintenance. 3. α, β test In fact, software developers cannot fully anticipate users' actual use programs. For example, the user may be wrong to understand command, or provide some strange data portfolios, may also confuse the designer's self-identified output information, and so on. Therefore, whether the software truly meets the final user's request, and should be conducted by the user a series of "acceptance tests". Acceptance tests can be both a non-formal test or have a planned, systematic test. Sometimes, the acceptance test has reached several weeks or even months, which continues to expose the error, leading to the development of extension. A software product may have many users, it is impossible to accept each user, at this time, the process called α, beta test is used, and the issues that seem to have only end users can find. Α test refers to the software development company organizes internal personnel to simulate various types of users to test the ultra-market software product (called α version), try to find errors and correct. The key to α test is to simulate the actual operating environment and users to operate the software products and do their best to cover all possible users. Software products adjusted by alpha tests are called β. Completed with the subsequent beta test refers to the actual use of a typical user in all aspects of the software development company actually uses the beta version in daily work, and requires the user to report an abnormal situation and propose criticism. The software development company is then changed and perfect for the beta version.
