Stage: Acceptance
User Acceptance Test (UAT) Plan
[PROJECT NAME]
Document Version: [x.x]
Date: [dd/mm/yy]
Contents
2.1 User Acceptance Definition
1 Document Management
When completing this document, please mark any section that is not required as ‘N/A’. A brief description of why the section is not required should also be included.
1.1 Contributors
Please provide details of all contributors to this document.
| Role | Department | Name |
| Owner | MIS | |
| Contributor | | |
| Contributor | | |
| Contributor | | |
1.2 Version Control
Please document all changes made to this document since initial distribution.
| Date | Version | Author | Section | Amendment |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
2 USER ACCEPTANCE TESTING
2.1 User Acceptance Definition
User Acceptance Testing should ensure that the application performs at an acceptable level for the Customer.
2.2 UAT Responsibilities
| Role | Name | Responsibilities |
| Project Manager | | Communication with Customer to agree format and scope of UAT |
| Agree acceptance criteria with the Customer prior to commencing UAT | ||
| Business Analyst | | Assist Customer with the creation of a detailed test plan |
| Test Co-ordinator (Business) | | Ensure that a detailed test plan is available for test users |
| Ensure that bugs identified during UAT are logged in the Defecr Tracker | ||
| Ensure testing takes place within agreed timeframes |
3 UAT STRATEGY
The User Acceptance Test Plan should be used to record the Customer’s sign off of the documented scenarios. It is recommended that detailed test plans be used to record the results of user testing.
The document is a high level guide, and is not intended as a replacement for any specific user acceptance testing procedures that individual areas might have.
| Consideration | Date Agreed | Details |
| Test Approach | | |
| Assumptions & Constraints | | |
| Setup of Test Environment | | |
| Test Scenarios | | |
| Test Period | | |
4 USER TESTING
User testing should be based on the pre agreed test scenarios or acceptance criteria. It should be noted if the scenarios have been sourced from the BRD, or if they have been identified subsequently.
| Identified in BRD | ||
| Scenario | Date Tested | Notes |
| | | |
| | | |
| | | |
| Identified Post BRD | ||
| Scenario | Date Tested | Notes |
| | | |
| | | |
| | | |
Any issues identified during UAT should be added to the MIS Test Log. It may be agreed that UAT can be signed off while some issues remain – please add the test log reference to the appropriate section above if this is the case.
5 UAT RESULTS
5.1 Open Issues
Please insert a copy of any open issues from the Test Log, together with details of why these issues remain open at the sign off of the Acceptance Stage.
5.2 Document Sign Off
| Business Project Manager | Name |
| Project Manager | Name |
Stage: Acceptance
User Acceptance Test (UAT) Plan
[PROJECT NAME]
Document Version: [x.x]
Date: [dd/mm/yy]
Contents
2.1 User Acceptance Definition
1 Document Management
When completing this document, please mark any section that is not required as ‘N/A’. A brief description of why the section is not required should also be included.
1.1 Contributors
Please provide details of all contributors to this document.
| Role | Department | Name |
| Owner | MIS | |
| Contributor | | |
| Contributor | | |
| Contributor | | |
1.2 Version Control
Please document all changes made to this document since initial distribution.
| Date | Version | Author | Section | Amendment |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
2 USER ACCEPTANCE TESTING
2.1 User Acceptance Definition
User Acceptance Testing should ensure that the application performs at an acceptable level for the Customer.
2.2 UAT Responsibilities
| Role | Name | Responsibilities |
| Project Manager | | Communication with Customer to agree format and scope of UAT |
| Agree acceptance criteria with the Customer prior to commencing UAT | ||
| Business Analyst | | Assist Customer with the creation of a detailed test plan |
| Test Co-ordinator (Business) | | Ensure that a detailed test plan is available for test users |
| Ensure that bugs identified during UAT are logged in the Defecr Tracker | ||
| Ensure testing takes place within agreed timeframes |
3 UAT STRATEGY
The User Acceptance Test Plan should be used to record the Customer’s sign off of the documented scenarios. It is recommended that detailed test plans be used to record the results of user testing.
The document is a high level guide, and is not intended as a replacement for any specific user acceptance testing procedures that individual areas might have.
| Consideration | Date Agreed | Details |
| Test Approach | | |
| Assumptions & Constraints | | |
| Setup of Test Environment | | |
| Test Scenarios | | |
| Test Period | | |
4 USER TESTING
User testing should be based on the pre agreed test scenarios or acceptance criteria. It should be noted if the scenarios have been sourced from the BRD, or if they have been identified subsequently.
| Identified in BRD | ||
| Scenario | Date Tested | Notes |
| | | |
| | | |
| | | |
| Identified Post BRD | ||
| Scenario | Date Tested | Notes |
| | | |
| | | |
| | | |
Any issues identified during UAT should be added to the MIS Test Log. It may be agreed that UAT can be signed off while some issues remain – please add the test log reference to the appropriate section above if this is the case.
5 UAT RESULTS
5.1 Open Issues
Please insert a copy of any open issues from the Test Log, together with details of why these issues remain open at the sign off of the Acceptance Stage.
5.2 Document Sign Off
| Business Project Manager | Name |
| Project Manager | Name |
It is true that any application which is used by large number of users across different geographical locations can become a perfect candidate for the advanced testing solution. Find more details about remote user testing visit here.
ReplyDelete