Acceptance Tests and Outcomes
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.
1. Deliverable 1.1: Changes to HR database, application, and extracts:
BRD ID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
1.1 | Make the required modifications to the HR application | Confirm that all new/changed fields have been correctly applied in the HR application | Debbie/Susan | 23/05/13 | Not all fields are showing under correct responsibility (e.g. some are only under HRMS Manager) HRS071-86 |
1.2 | Make the required modifications to the HR Self Service screens | Confirm that all new/changed fields have been correctly applied in the HR Self Service screens | Debbie | 17/05/2013 | Pass |
1.3 | Update the HR -> HESA extract facility, to retrieve the new and modified fields from the HR database and upload them to the HESA extract database | Confirm that all pre-existing, unchanged fields are operating correctly in the HESA universe. Confirm that the new/changed fields are appearing correctly in the HESA universe. | Susan | 17/05/2013 | Pass |
| 1.4 | Update the HR -> PPIPMI extract facility, to retrieve the new and modified fields from the HR database and upload them to the PPIPMI extract database | Confirm that the new/changed fields are appearing correctly in the PPIPMI universe. | N/A - PPIP removed from scope on 21-Mar-13 |
2. Deliverable 1.2: Changes to HESA and HESA Archive database, application, extracts, and BOXI universes:
BRD ID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
2.1 | Add the new fields and make the required modifications to the existing fields on the HR HESA database | Confirm that all pre-existing, unchanged fields are operating correctly in the HESA universe. Confirm that the new/changed fields are appearing correctly in the HESA universe. | Susan | 17/05/2013 | Pass |
2.2 | Add the new fields and make the required modifications to the existing fields on the HR HESA Archive database | Confirm that all pre-existing, unchanged fields are operating correctly in the HESA Archive universe. Confirm that the new/changed fields are appearing correctly in the HESA Archive universe. | Susan | 27/05/2013 | Pass |
2.3 | Modify the archive process to include the new/modified fields | Run the archive process. Confirm that all pre-existing, unchanged fields are operating correctly in the HESA Archive universe. Confirm that the new/changed fields are appearing correctly in the HESA Archive universe. | Susan | 27/05/2013 | Pass |
| 2.4 | Modify the HR HESA application to include the new/modified fields | Confirm that all pre-existing, unchanged fields are operating correctly in the new HESA application. Confirm that all new/changed fields are operating correctly in the new HESA application. | Susan/Debbie | 21/05/2013 | Pass |
| 2.5 | Update the HR HESA BOXI universe to display the new/modified fields | Confirm that all pre-existing, unchanged fields are operating correctly in the HESA universe. Confirm that the new/changed fields are appearing correctly in the HESA universe. | Susan | 17/05/2013 | Pass |
| 2.6 | Update the HR HESA Archive BOXI universe to display the new/modified fields | Confirm that all pre-existing, unchanged fields are operating correctly in the HESA Archive universe. Confirm that the new/changed fields are appearing correctly in the HESA Archive universe. | Susan | 27/05/2013 | Pass |
2b. Deliverable 1.2: Supporting data from PURE:
BRDID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
2.7 | (GaSP) Provide and populate the required Research fields in PURE | Confirm that the data provided by GaSP is valid, before submitting it to IS Apps for upload to the HESA tables | Susan | 27/05/2013 | Pass in Test, but diferent file to be provided for Live |
2.8 | (GaSP) Provide a csv download file of the required Research fields | Confirm that the data provided by GaSP is valid, before submitting it to IS Apps for upload to the HESA tables | Susan | 27/05/2013 | as above |
2.9 | Upload the csv data file into the HR HESA Person table | Confirm that the new Research fields from the csv file are appearing correctly in the HESA universe | Susan | 27/05/2013 | as above |
3. Deliverable 1.3: Changes to eRecruitment database, application, extract, and BOXI universe:
BRD ID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
3.1 | Add and/or modify the SOC field in the eRecruitment database (to be performed by the business area). This may require the Business Area Manager to coordinate with CORE for a supporting eRecruitment data update | Confirm that the new/changed SOC field is operating correctly in the eRecruitment application. | Debbie | 16/05/2013 | Pass |
3.2 | Make the required SOC modification to the eRecruitment application (to be performed by the business area) | Confirm that the SOC field's new list of values is correct in the eRecruitment application. Confirm that the new SOC values have been correctly applied to records in the eRecruitment application. | Debbie | 16/05/2013 | Pass |
| 3.3 | Update the eRecruitment to HR extract to retrieve the added/modified SOC field | Confirm that the new SOC values for records extracted from eRecruitment are appearing correcly in the HR application. | Debbie | 23/05/2013 | Pass |
| 3.4 | Update the eRecruitment BOXI universe to display the new/modified SOC field | Confirm that the new SOC values are appearing correctly in the eRecruitment universe. | N/A - eRecruitment universe changes removed from scope in the Design Review meeting |
4. Deliverable 1.4: Changes to PPIPMI database and BOXI universe:
BRD ID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
4.1 | Add the new fields and make the required modifications to the existing fields on the HR PPIPMI database | Confirm that the new/changed fields are appearing correctly in the PPIPMI universe. | N/A - PPIP removed from scope on 21-Mar-13 | ||
4.2 | Update the HR PPIPMI BOXI universe to display the new/modified fields | Confirm that the new/changed fields are appearing correctly in the PPIPMI universe. | N/A - PPIP removed from scope on 21-Mar-13 |
5. Deliverable 2.1: Update the HESA extract facility for required final return functionality:
BRD ID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
5.1 | Modify the HR HESA extract files to include the new/modified fields | Confirm that all fields are appearing correctly in the HESA xml file | Susan | 22/05/2013 | Pass |
6. Deliverable 2.2: Update the HESA submission method:
BRD ID | Requirement | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome (PASS / FAIL) |
6.1 | Change the Staff flat file structure to use XML | Confirm that all Staff fields are appearing correctly in the HESA xml files | Susan | 23/05/2013 | Pass |
| 6.2 | Change the Contract flat file structure to use XML | Confirm that all Contract fields are appearing correctly in the HESA xml files | Susan | 23/05/2013 | Pass |
6.3 | Remove the Grades file | Confirm that no Grades file is produced | Susan | 23/05/2013 | Pass |
Non-Functional Requirements
No change to existing non-functional requirements.
BRD Ref | Notes on Test and/or Test Outcome |
|
|
|
|
|
|
Other UAT Scenarios
Open Issues
Any issues identified during UAT must be added to the Jira 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 |
| 23 |
|
|
| 86 |
|
|
|
|
|
|
Link to JIRA Test Log
Document Sign Off
Please add other signatories where required
Project Manager | Jill Nicoll | Draft plan signed off in Analysis Review meeting, 19/12/12 |
Project Sponsor represented by Business Area Manager | Susan McLaren | Draft plan signed off in Analysis Review meeting, 19/12/12 |
Business Analyst | Jill Nicoll | Draft plan signed off in Analysis Review meeting, 19/12/12 |