3 Forms of Acceptance Testing and their Application

Any application has to be tested. One highly respected programmer said: “programs that are not tested, are not working.”

Acceptance testing is performed based on a set of common test cases and scenarios developed on the basis of the requirements for the application.

The decision to conduct acceptance test is taken when:

• the product has reached the required level of quality;
• customer familiar with the Product Acceptance Plan or other document, which describes a set of actions related to the acceptance test, date, charge, etc.

Alpha-and Beta-Testing

Upon completion of system testing software can be transmitted to the user to perform acceptance tests. If users belong to the same company as the developer, such testing is usually called the alpha testing. If users are customers who are willing to work with the software product before its official availability, then this testing is called beta testing.

And alpha-and beta-testing are appropriate forms of control tests (pilot tests), in which the system is installed on a trial basis in order to identify defects.

Benchmark Tests

Another form of acceptance tests are the Benchmark test, when a customer performs a predefined set of test cases that simulate typical conditions in which the system will work after introduction into service.

For benchmark tests can be used test-cases that have been developed and debugged by your testing organization and which at the same time have been reviewed and approved by the customer.

Upon completion of the control and benchmark tests the customer should inform you what the requirements are not met, and what should be changed so that you can go to the final test.

Installation Test

The final type acceptance testing is the Installation test, under which the completed version of the software product installed on the customer’s site to get his confirmation, that the product meets all the requirements and the customer agrees to its delivery.

Acceptance testing phase lasts as long as the customer does not make a decision on the administration of applications for revision or issuance of the application.