Acceptance Testing

The purpose of the acceptance testing phase is to demonstrate that the system meets requirements in the operational environment. The development team does not perform the acceptance test. Testing is executed to see if the project meets the original client requirements, and it is only considered complete when all tests specified in the acceptance test plan have been run successfully.

Acceptance testing guarantees compliance with end-user requirements and determines whether a system integrates into the operational environment. Acceptance testing is done after the completion of system testing. At the conclusion of systems testing, there is a meeting to decide if the application is ready for acceptance testing. All known critical defects should be fixed and tested prior to the start of acceptance testing. The goal is to make no more changes to the application or environment once acceptance testing begins.

During acceptance testing, the IT development team assists the test team and may execute the acceptance tests under the direction of the acceptance test team. The development team corrects any errors uncovered by the tests. Acceptance testing is considered complete when all tests specified in the acceptance test plan have been run successfully and the system has been formally accepted. The development team then delivers final versions of the software and system documentation (the user guide and system description) to the customer. The purpose of an acceptance test is to allow the user to verify the following:

• The system is stable, works as an integrated system, and is presented to the users as a product.

• Databases supporting the system have the scope to cover the business correctly.

• Data entry and reports all present data in a correct manner.

• The system interacts correctly with existing systems.

• Business processes are correctly reflected within the system and allow defined business procedures to operate as required.

• Error processing is handled effectively and user help facilities are completed and usable.

• System administration functions and system security are correctly supported.

• Batch processing within the system and with related systems works within the sequences and timings necessary to support the business.

• The system is capable of handling multiple transactions and of supporting concurrent users.

At the end of acceptance testing, when all acceptance tests have been completed, a final report documenting testing results is prepared and maintained in the project folder. This includes a final detailed report on each test, in addition to an overall summary that gives an overview of the testing process and records how many test items passed during each round of testing.

Was this article helpful?

0 0

Post a comment