(UAT)User Acceptance Testing


Introduction- is a type of testing performed by the end user or the client to verify/accept the software system before moving the software application to the production environment. UAT is done in the final phase of testing after functional, integration and system testing is done.

Purpose of UAT :-
The main Purpose of UAT is to validate end to end business flow. It does not focus on cosmetic errors, spelling mistakes or system testing. User Acceptance Testing is carried out in a separate testing environment with production-like data setup. It is kind of black box testing where two or more end-users will be involved.
Who perform UAT:
1. Client 2. End users

Need of User Acceptance Testing :-
Need of User Acceptance Testing arises once software has undergone Unit, Integration and System testing because developers might have built software based on requirements document by their own understanding and further required changes during development may not be effectively communicated to them, so for testing whether the final product is accepted by client/end-user, user acceptance testing is needed.
1. Developers code software based on requirements document which is their “own” understanding of the requirements and may not actually be what the client needs from the software.
2. Requirements changes during the course of the project may not be communicated effectively to the developers.

Acceptance Testing and V-Model:-
In VModel, User acceptance testing corresponds to the requirement phase of the Software Development life cycle(SDLC).


Prerequisites of User Acceptance Testing:-
Following are the entry criteria for User Acceptance Testing:

  • Business Requirements must be available.
  • Application Code should be fully developed
  • Unit Testing, Integration Testing & System Testing should be completed.
  • No Showstoppers, High, Medium defects in System Integration Test Phase –
  • Only Cosmetic error is acceptable before UAT.
  • Regression Testing should be completed with no major defects.
  • All the reported defects should be fixed and tested before UAT.
  • Traceability matrix for all testing should be completed.
  • UAT Environment must be ready.
  • Sign off mail or communication from System Testing Team that the system is ready for UAT execution.

How to do UAT Testing :-
UAT is done by the intended users of the system or software. This type of Software Testing usually happens at the client location which is known as Beta Testing. Once Entry criteria for UAT are satisfied, following are the tasks need to be performed by the testers.


  • Analysis of Business Requirements
  • Creation of UAT test plan
  • Identify Test Scenarios
  • Create UAT Test Cases
  • Preparation of Test Data(Production like Data)
  • Run the Test cases
  • Record the Results
  • Confirm business objectives

Step 1) Analysis of Business Requirements:-
One of the most important activities in the UAT is to identify and develop test scenarios. These test scenarios are derived from the following documents:
– Project Charter
– Business Use Cases
– Process Flow Diagrams
– Business Requirements Document(BRD)
– System Requirements Specification(SRS)

Step 2) Creation of UAT Plan:-
The UAT test plan outlines the strategy that will be used to verify and ensure an application meets its business requirements. It documents entry and exit criteria for UAT, Test scenarios and test cases approach and timelines of testing.

Step 3) Identify Test Scenarios and Test Cases:- Identify the test scenarios with respect to high-level business process and create test cases with clear test steps. Test Cases should sufficiently cover most of the UAT scenarios. Business Use cases are input for creating the test cases. Step 4) Preparation of Test Data:-
It is best advised to use live data for UAT. Data should be scrambled for privacy and security reasons. Tester should be familiar with the database flow.

Step 5) Run and record the results:-
Execute test cases and report bugs if any. Re-test bugs once fixed. Test Management tools can be used for execution.

Step 6) Confirm Business Objectives met:-
Business Analysts or UAT Testers needs to send a sign off mail after the UAT testing. After sign-off, the product is good to go for production. Deliverables for UAT testing are Test Plan, UAT Scenarios and Test Cases, Test Results and Defect Log.

Mr. Arshad Hussain, Assistant Professor, School of Computer Applications, Career Point University, Kota

Leave a Reply

Your email address will not be published. Required fields are marked *