Acceptance Tests and Outcomes
1. UAT Scenarios from Business Requirements Document
User testing should be based on the test scenarios and acceptance criteria identified in the Business Requirement Document. Any deviation from these scenarios should be noted here.
Quick review of Open JIRAs from first run of Integration testing and UAT in Nov 2016 , ahead of Worktribe Upgrade to v2.2 - project then put on hold for 12 months
|
BRD Ref |
Scenario / Acceptance Criteria |
Tested By |
Date Tested |
Outcome (PASS / FAIL) |
|
STU252-9 |
Organisation Units associated with PI/CI/Budget Lines |
|
|
|
|
STU252-15 |
Group Bases Permissions |
|
|
|
| STU252-7 | Duplicate Rows on FCT_Budget_lines | |||
| STU252-21 | Mismatch between FCT tables | |||
| STU252-6 | Actual Spend only exists at project level | |||
|
STU252-25 |
date format error |
|
|
|
|
BRD Ref |
Notes on Test and/or Test Outcome |
|
|
|
|
|
|
|
|
|
2. Other UAT Scenarios
Additional test scenarios used in testing but not sourced from the Business Requirements Document should be identified here. The justification for including the scenario in the UAT must also be recorded.
|
Ref |
Test Scenario and Acceptance Criteria |
Tested By |
Date Tested |
Outcome (PASS / FAIL) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ref |
Notes on Test and/or Test Outcome |
|
|
|
|
|
|
|
|
|
3. Open Issues
Any issues identified during UAT must be added to the Test Log. Please summarise or insert a copy of any open issues from the JIRA Test Log. It may be agreed that UAT can be signed off while some issues remain open please provide details of the UAT impact of each open issue.
|
BRD Ref |
JIRA Test Log Ref |
Issue Summary |
Impact on UAT Sign Off |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[Link to updated JIRA Test Log ]
4. Document Sign Off
[Please add other signatories where required]
|
Project Manager |
Name |
Date Signed Off |
|
Project Sponsor |
Name |
Date Signed Off |
|
Business Analyst |
Name |
Date Signed Off |
|
Add other signatories here |
|
|