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 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
|
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 |
Karen Stirling |
|
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.
|
Elaine Wighton / Sue Woodger |
|
Technical Architect |
· Validation of UAT environment |
Riky Harris |
|
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 |
Paul Gorman |
|
Testers |
· Execute test scripts/cases · Document test results |
Change Based Feed / Bulk Feed (Alex Forrest / Paul Gorman) Self Reg UI (Paul Gorman / Louise Gilchrist / Abigail Kleboe /Samantha Green / Fiona Martin / Shona Newton) VRS Admin for Library Patrons (Paul Gorman / Andrew Kirk / Samantha Green / Kirsty Campbell / Louise Gilchrist / Abigail Kleboe ) Front Office (Paul Gorman / Andrew Kirk) VRS (Chris McKay / Adam Wheavil) Card (Paul Maclachlan) Door Access (Lyndsey Archibald) |
Test Requirements
-
- UAT will take place beginning on 7th November and end on 25th October 216
- UAT will take place in Main Library (Some testers may choose to perform some testing from their regular work location where this is possible and is agreed in advance with the Project Manager and Project Sponsor
- Participants will receive training, guidance and instructions prior to the start of UAT
- 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 Test Log/JIRA or other format specified
- Issues recorded in the JIRA Test Log (and/or other test documentation) 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 |
Area Represented |
Testing Area of Responsibility |
|
Paul Gorman |
IS User Services Division - Helpdesk |
Change Based Feed / Bulk Feed, |
|
Alex Forrest |
IS Library & University Collections |
Change Based Feed / Bulk Feed |
| Paul Gorman, Andrew Kirk (see above) | IS User Services Division - Helpdesk | Self Reg UI, VRS Admin |
|
Paul MacLachlan |
IS User Services Division - Card Services |
Card |
|
Lyndsey Archibald |
IS ITI - Card (Door Access) |
Card Door Access |
|
Chris McKay |
IS Application Service Management |
VRS Changes |
| Hugh Brown / Adam Wheavil | IS Application Management | VRS, IDM |
Test Schedule
|
Activity |
Responsibility |
Target Date |
Date Completed |
|
Confirm testers for UAT |
Project Sponsor / Business Assurance Coordinator |
Done |
Done |
|
Confirm test scenarios, test data and scripts/cases |
Project Sponsor / Business Assurance Coordinator Business Analyst |
Done |
Done |
|
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 |
Done |
Done |
|
Oversee testing by UAT participants |
Project Sponsor / Business Assurance Coordinator |
Done |
|
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 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.
- Testers will test the functionality documented in the approved BRD (taking into account any changes in business requirement subsequently agreed by the Project Team)
- Resources identified in this plan are available to conduct the UAT and address issues as they are raised by the test team.
- Business Analyst should record any additional assumptions here
The Project Manager must notify the Project Sponsor if any of these assumptions are not correct before commencing the UAT.