User Acceptance test
The purpose of User Acceptance Testing (UAT) is to ensure that the solution by the project meets the functional and non-functional requirements specified in the business requirements. UAT may also identify issues that have not been specified in the BRD such as those relating to usability. UAT is the final step before rolling out the solution. UAT is typically carried out by end users in an environment that closely models the real world. A well-managed UAT process will give the Project Sponsor, project team and end users confidence that the solution being delivered meets the requirements.
This document outlines the plan for UAT of the project deliverables. This document is a high level guide and will initially be developed during requirements gathering as part of the Business Analysis stage. Detailed test scripts/cases will be developed as part of the UAT Plan and will be used to record the results of user testing. Testing itself and the formal recording of UAT results takes place during the Acceptance stage.
Roles and Responsibilities and Test Participants
· Communication with the Business Assurance Coordinator to agree format and scope of UAT
· Ensure acceptance criteria are agreed prior to commencing UAT
· Validation of UAT environment including BOXI
CMS Service Manager & Web CMS Support Officer
· Ensure that a detailed test scripts/cases, scenarios and instructions are available for test users prior to the start of testing
· Ensure that issues identified during UAT are logged in the Test Log
· Ensure testing takes place within agreed timeframes
· Execute test scripts/cases
· Document test results
- UAT will take place week beginning 3 February in UWP
- A fully configured TEST environment including all of the functionality and adequate TEST data will be provided for UAT
- Test scripts/cases and scenarios will be prepared prior to the start of UAT
- Technical and business support will be provided for test participant during UAT
- UAT participants will conduct the tests and record results in the UAT document
- The UAT environment will be available and fully configured ahead of the UAT.
- The business team has reviewed and accepted functionality identified in the Business Requirements Document (BRD) and System Design Document (SDS).
- Code walkthroughs/reviews have been completed by the Development Team and signed off as part of the Peer Project Build Review (PPBR)
- Integration testing, including where relevant load and performance testing, has been completed and signed off as part of the Peer Project Integration Review.
- Resources identified in this plan are available to conduct the UAT and address issues as they are raised by the test team.
The Project Manager must notify the Project Sponsor if any of these assumptions are not correct before commencing the UAT.