The purpose of UAT: 

The testing of the product or application is validated at the end of the software development life cycle process. After unit testing, integration testing, system testing, regression testing, performance testing are conducted, then after user acceptance testing is performed. UAT safeguards against unfinished, ineffective and faulty software products being released. 

The user requirements are thoroughly reflected through the UAT testing process. Potential problems are identified using this testing method.  

The responsibility of conducting UAT:  

User Acceptance Testing (UAT) is generally conducted by end-users, stakeholders, clients etc.  These members are basically held responsible for testing the software product or application in a real-time production environment.  

Internal functional experts also play a crucial role in UAT, as test management and UAT cycles are shaped by them and then the results are interpreted.   

Types of UAT: 

1. Beta testing: It is a testing method wherein a beta version (which is 80% to 95% completed (approx.)) of a product or application is tested by beta testers in a real-time production environment.   

2. Contract acceptance testing: The testing of software is carried out based on specifications and specific criteria that are being defined in the contract by the project team. 

3. Operational acceptance testing: Predefined workflow is focused on the operational and software readiness, such as product reliability, compatibility and stability.  

4. Regulation acceptance testing: This test focuses on making sure that the software is aligned with legal regulations and rules.