User Acceptance Testing
Acceptance Test Strategy
UAT testing
- is the responsibility of the HR Systems team
- will be performed in the Test environments
- will take place in the testers' normal working area
- is currently scheduled to start on 24th April 2013
- feedback will be managed via the project's Jira Test Log
Fortnightly project meetings will continue throughout the testing stage
The Acceptance Sign-off Review milestone is currently scheduled for 22nd May 2013.
Test Scenarios and Acceptance Criteria
1. Deliverable 1.1: Changes to HR database, application, and extracts:
BRD ID | Requirement | Scenario / Acceptance Criteria |
1.1 | Make the required modifications to the HR application | Confirm that all new/changed fields have been correctly applied in the HR application |
| 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 |
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. |
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. |
2. Deliverable 1.2: Changes to HESA and HESA Archive database, application, extracts, and BOXI universes:
BRD ID | Requirement | Scenario / Acceptance Criteria |
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. |
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. |
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. |
| 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. |
| 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. |
| 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. |
2b. Deliverable 1.2: Supporting data from PURE:
BRD ID | Requirement | Scenario / Acceptance Criteria |
2.7 | (GaSP) Provide and populate the required Research fields in PURE |
|
2.8 | (GaSP) Provide a csv download file of the required Research fields |
|
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. |
3. Deliverable 1.3: Changes to eRecruitment database, application, extract, and BOXI universe:
BRD ID | Requirement | Scenario / Acceptance Criteria |
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. |
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. |
| 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. |
| 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. |
4. Deliverable 1.4: Changes to PPIPMI database and BOXI universe:
BRD ID | Requirement | Scenario / Acceptance Criteria |
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. |
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. |
5. Deliverable 2.1: Update the HESA extract facility for required final return functionality:
BRD ID | Requirement | Scenario / Acceptance Criteria |
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 files |
6. Deliverable 2.2: Update the HESA submission method:
BRD ID | Requirement | Scenario / Acceptance Criteria |
6.1 | Change the Staff flat file structure to use XML | Confirm that all Staff fields are appearing correctly in the HESA xml files |
| 6.2 | Change the Contract flat file structure to use XML | Confirm that all Contract fields are appearing correctly in the HESA xml files |
6.3 | Remove the Grades file | Confirm that no Grades file is produced |