Software Acceptance Testing: The Last Hurdle for the Software

Acceptance Testing is the formal testing conducted to determine whether a software system satisfies its acceptance criteria and to enable buyer to determine whether to accept the system or not. This is designed to determine the fitness of the software for use. Apart from functionality of application, other factors related to business environment also play an important role. This is a part of black box testing and is done prior to the release of the software. People refer this also as functional testing, application testing, confidence testing, final testing, and factory acceptance testing etc.

The acceptance testing can be performed either by the system provider or the customer. These are two different methods of acceptance testing depending on the agency that executes it. In a situation where the user or customer becomes the proprietor of the software and carries out the acceptance testing it is known as user acceptance testing, beta testing, or site acceptance testing.

The main requirement for starting acceptance testing is that the full completion of the system. On system completion the testing contains a whole group of tests known as cases. Each of these test cases works on a specific operating part of the features of the system. The result of the test is based on the Boolean 'pass or fail' system. Irrespective of the results, whether good or bad, there is no level of success or failure. Normally, the test is performed near about the location where the system is located.

The input to the test cases is either data or a formal description of tests to be performed and results anticipated. Based on these inputs the case tests are run. The input data is a direction for the testers to know the instructions to be followed and also the desired results. A comparison of the case test is made with the desired results. In case both of them match completely the case test is considered as a pass. Otherwise the system is rejected unless certain conditions are agreed upon prior to testing.

The main objective of acceptance testing is to provide confidence for both the provider and the user for satisfactory functioning of the system. During the last phase of acceptance testing any undetected quality defects could be found and rectified. Once the system acceptance is completed satisfactorily for both parties, there will be a final system completion report from the provider and acceptance report from the user. With this it is concluded that the contract has been honored and the system delivered.