User Acceptance Testing

User Acceptance Testing or UAT is the last step prior to completion of any application. The Users must ensure the system is stable and meets the minimum quality criteria before proceeding to system deployment.

This type of testing is helpful for any end users. It boosts up their confidence as they are sure they will be getting an application with expected results. This kind of testing also help the bugs to be keep away from the application without interfering it. User Acceptance test should be conducted by the end users of the system and monitored by an independent testing organization.

User Acceptance Testing could be in the form of

• Alpha Testing - Where test are conducted at the development site by the end users. Any type of abnormal behaviour of the system is noted and rectified by the developers. Environment can be controlled a little bit in this case.
• Beta Testing - Where test are conducted at customer site and development team do not have any control on the test environment. In beta testing, users play the role of testers. The beta test is a live application of the software in an environment that cannot be controlled by the developer.

Entry criteria for User Acceptance Testing:

• Integration testing signed off should be received.
• Business requirements and functional requirements have been met.
• UAT test cases are ready for execution.
• UAT testing environment should be ready.
• Necessary access for testing should be obtained.
• No critical bugs should be present.
• All the modules committed for testing should be tested and test report should be handed over to client.

Exit criteria for User Acceptance Testing:

• No critical defects found.
• Minimum outstanding medium priority defects should be found.
• Business process is workings satisfactorily.
• UAT close off meeting held.