- The following are the entry criteria for User Acceptance Testing:
- All business requirements should be available.
- Application Code must be fully developed
- Unit Testing, Integration Testing & System Testing must be fully completed
- No Showstoppers, High, Medium defects in System Integration Test Phase –
- Only Cosmetic errors are deemed acceptable before UAT
- Regression Testing must be fully completed with no major defects
- All the reported defects must be fixed and tested before UAT
- The traceability matrix for all testing must be fully executed
- UAT Environment setup should be ready
- Sign-off email or communication from System Testing Team should be initiated before UAT execution
User Acceptance Testing is usually conducted by the intended users of the system or software. This type of Software Testing is conducted mostly at the client location which is referred to as Beta Testing. Once the Entry criteria for UAT are fully met, the following tasks are needed to be performed by the testers.
- Analysis of Business Requirements
- User Acceptance Test plan creation
- Test Scenarios identification
- User Acceptance Test Cases Creation
- Test Data Preparation (Production-like Data)
- Running the Test cases
- Recording the Results
- Confirming all business objectives
Step 1) Analysis of Business Requirements
The most important activity in User Acceptance Testing is to identify and develop test scenarios. These test scenarios are usually derived from the below-stated documents:
Business Use Cases
Process Flow Diagrams
Business Requirements Document(BRD)
System Requirements Specification(SRS)
Step 2) Creation of a User Acceptance Testing Plan:
The User Acceptance Testing test plan strategy outlines what will be used to verify and ensure an application meets its business requirements. It also documents the entry and exit criteria for User Acceptance Testing, test scenarios and test case approaches, and the estimated timeline of testing.
Step 3) Test Scenarios and Test Cases identification
Identifying the test scenarios concerning high-level business processes, and creating test cases with clarified test steps. Test Cases should sufficiently cover most of the User Acceptance Testing scenarios. Business Use cases are the usual input for creating the User Acceptance Testing test cases.
Step 4) Preparation of Test Data:
It is best advised to deploy live data for User Acceptance Testing. However, all live data should be scrambled for ensuring privacy and security reasons and the test team must be familiar with the database flow.
Step 5) Execute the test cases and record the results:
Involves executing test cases and reporting bugs if any. Also ensuring Re-testing for bugs once fixed. Test Management tools can be deployed for execution.
Step 6) Confirm Business Objectives met:
Business Analysts or User Acceptance Testers need to send a sign-off closure email after the User Acceptance Testing. After sign-off, the product is usually considered good for production. The deliverables for User Acceptance Testing are Test Plan, User Acceptance Testing Scenarios and Test Cases, Test report, Sign off, and Defect Logs.
Exit criteria for User Acceptance Testing:
Before moving into production, the following exit criteria need to be considered:
- Ensuring that No critical defects are open
- All Business process works satisfactorily
- User Acceptance Testing Sign off meeting with all stakeholders