User Acceptance test
Definition
The purpose of User Acceptance Testing (UAT) is to ensure that the solution by the project meets the functional and non-functional requirements specified by the business requirements. 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 post-deployment changes. Rather than being specified in the Business Requirements Document (BRD), these changes have been specified in a series of Jira log items, and in the PDF meeting note.
Detailed test scripts/cases must be developed by the business testers, as part of the UAT Plan. These will then be used to record the results of user testing. Testing itself, and the formal recording of UAT results, take place during the Acceptance stage.
Roles and Responsibilities
Role | Responsibilities | Name |
Project Manager | · Communication with the Business Assurance Coordinator to agree format and scope of UAT · Ensure acceptance criteria are agreed prior to commencing UAT | Adam Wadee |
Business Analyst | · Assist Business Assurance Coordinator with the creation of a detailed test plan · Review scripts/cases and scenarios for accuracy, completeness and sequencing. · Confirm test data is correct. | Adam Wadee Jill Nicoll |
Business Assurance Coordinator | · 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 | Craig Smith |
Technical Architect | · Validation of UAT environment | Neil Grant |
Testers | · Execute test scripts/cases · Document test results | Craig Smith Gary Halliday Susan Hamilton Morag Laidlaw Richard Yardley |
Test Requirements
- UAT for Jira changes will start on 10th September 2012 and end on 14th September 2012
- UAT for PDF changes will start on 24th September and end on 5th October
- UAT will take place at the testers’ normal work location
- 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 by the testers prior to the start of UAT
- Technical and business support will be provided for test participants during UAT
- UAT participants will conduct the tests and record results in the JIRA Test Log
- Issues recorded in the JIRA Test Log will tracked by the Project Manager and Project Sponsor
Test Participants
Testing participants include representative from all areas involved in the solution. Testers and their specific areas of focus are identified in the table below:
Name | Unit Represented | Testing Area of Responsibility |
Craig Smith | ERI | ERI |
Gary Halliday | RGS (SCE) | RGS (SCE) |
Susan Hamilton | HSS | HSS |
Morag Laidlaw | MVM | MVM |
Richard Yardley | SCE | SCE |
Test Schedule
Activity | Responsibility | Target Date | Date Completed |
Confirm testers for UAT | Project Sponsor / Business Assurance Coordinator | 10/09/12 |
|
Confirm test scenarios, test data and scripts/cases | Project Sponsor / Business Assurance Coordinator Business Analyst | 10/09/12 |
|
Ensure UAT environment is configured for testing i.e. new functionality and test data is migrated to the TEST environment prior to the start of UAT
| Project Sponsor / Business Assurance Coordinator Business Analyst Systems Analyst / Designer Technical Architect | 10/09/12 |
|
Oversee testing by UAT participants | Project Sponsor / Business Assurance Coordinator | 10/09/12 – 24/09/12 |
|
All upgraded functionality and test data will be migrated to the test environment prior to the start of user acceptance testing.
Assumptions
- The UAT environment will be available and fully configured ahead of the UAT.
- The business team has reviewed and accepted the change requirements identified in the Jira log items and the PDF meeting note
- Testers will test the functionality documented in the Jira log items and the PDF meeting note
- Resources identified in this plan are available to conduct the UAT testing, and to address any testing issues as they are raised by the test team.