Software acceptance test

Software acceptance test

Software acceptance testing refers to the testing activities that testers check whether the software conforms to the software specifications and user needs .

Acceptance testing is the last step of software testing , It is also the most critical element , It is related to the product quality of software development companies , It is also related to whether the products of the demander can be successfully launched , So acceptance testing is also called delivery testing .

Software acceptance test content

Software acceptance testing has many contents , It is mainly divided into the following points ：

（1） Product specification test ;

（2） User interface and usability testing ;

（3） Compatibility test ;

（4） Installability and recoverability test ;

（5） Document the test .

Points for attention in software acceptance testing

（1） The tester must write a formal 、 Separate acceptance test report ;

（2） The acceptance test must be carried out in the actual user operating environment ;

（3） Performed jointly by the user and the testing department .

Prerequisites and steps of software acceptance test

Premise ： The system or software product has been tested for system and function .
step ：

（1） Develop test plans and acceptance criteria ;

（2） Establish test environment , Design test cases , And reviewed ;

（3） Prepare test data , Execute test case , Record test results ;

（4） Analyze test results , Analysis of test results according to acceptance criteria , Make acceptance and test evaluation ;

（5） Prepare software acceptance test report .

Software acceptance testing includes ：
Formal acceptance test
Informal acceptance test ( Include α Testing and β test )

Formal acceptance test

Formal acceptance testing of software requires very strict management , It is the continuation of system testing , The test case of this acceptance test shall be a subset of the system test .

advantage

The functions and features to be tested are known

The test details are known and can be evaluated

This test can be performed automatically , Support regression testing

The test process can be evaluated and monitored

Acceptance criteria are known

shortcoming

It requires a lot of resources and plans

These tests may be the re implementation of system tests

Defects caused by subjective reasons in the software may not be found , This is because you only look for defects that you expect to find

Informal acceptance test

Informal acceptance testing is not as strict as formal acceptance testing , There is no need to execute the specified test case , It can be decided by the tester , However, when formulating test cases, the main functions that need to be tested must be constrained according to the actual situation of the project .
 

1.α test （ Internal measurement ）

α The test is performed by a user In the development environment Test carried out , It can also be controlled test conducted by users inside the company under simulated actual operation environment ,α Testing cannot be done by programmers or testers .

2.β test （ Public survey ）

β Testing is the testing of multiple users of the software in the actual use environment of one or more users . Developers are usually not at the test site ,β Testing cannot be done by programmers or testers .

Software test sequence ： Formal test ->α test （ Internal measurement ）->β test （ Public survey ）