Why bother UAT?
User Acceptance Testing (UAT) 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.
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.
How to UAT?
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:
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)
In PPL, we are given some sort of raw Backlog at the start of our project. From which, we made a much neater PBI to refer on every time we are starting a new sprint.
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.
In PPL, we created our UAT Plan beforehand usually a day prior. We utilizes Google Sheets to make a beautiful UAT Plan.
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.
In PPL, we also clearly define all the necessary steps to achieve the exit criteria. It is very fine defined because the tester will not be the same with the one who developed it.
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.
In PPL, we also prepare all the data needed to test the particular features. We even made a special credentials for UAT purposes.
Step #5: Run and Record The Result
Execute test cases and report bugs if any. Re-test bugs once fixed. Test Management tools can be used for execution.
In PPL, we run the UAT synchronously with our lecture and the client via Zoom. On special occasions where our time schedules don’t meet, we record.
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.
In PPL, we only continue to the next sprint if and only if we have a go from our lecture and client. This assures that the business objectives of every sprint will always meet before proceeding to the next one.
