Functional Testing
See attached document for more detail on how the tests have been run: https://www.projects.ed.ac.uk/webfm_send/1421
1. Deliverable 1.1: Changes to HR database, application, and extracts:
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
1.1 | Confirm that all new/changed fields appear in the HR application | Alyson Shaw | 17/04/13 | FAILed originally, but Jira successfully addressed and closed. so now PASS | Initially had problem viewing the fields but worked out how to fix that and did so (implementation plan to be updated). Identified the following issues: https://www.jira.is.ed.ac.uk/jira/browse/HRS071-27 Note that this is a very minor point and would not affect system functioning normally |
1.2 | Confirm that all new/changed fields appear in the HR Self Service screens | Alyson Shaw | 17/04/13 | PASS |
|
1.3 | Confirm that the new/changed fieldsappear in the HR extract. | Alyson Shaw | 17/04/13 | PASS |
|
| 1.4 | Confirm that the new/changed fields appear in the PPIPMI extract. Note: PPIP de-scoped March 2013 | N/A |
2. Deliverable 1.2: Changes to HESA and HESA Archive database, application, extracts, and BOXI universes:
2b.
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
2.1 | Confirm that the new/changed fields appear in the HESA database. | Alyson Shaw | 17/04/13 | PASS |
|
2.2 | Confirm that the new/changed fields appear in the HESA Archive database. | Alyson Shaw | 17/04/13 | PASS |
|
2.3 | Run the archive process. Confirm that the new/changed fields appear in the HESA Archive universe. |
|
|
| I have not run the archive process because it will insert the records with archive year of 2012 instead of 2013 (it sets year by subtracting 7 months from run-date) . This would result in there being 2 archives for 2012 on the table which could cause confusion and introduce problems in testing. This is existing design of the archive - think designed this way as not meant to be run till after the hesa return has been submitted - and hesa return as at 31-July. However the universe does have placeholders for the new data items. AS 18/04 |
2.4 | Confirm that all new/changed fields appear in the new HESA application. Note: The new Apex forms will be implemented to Test at a later date (their development has been delayed by the scheduling of Oracle's Apex course.) |
| tbc | tbc | to be tested at a later date |
2.5 | Confirm that the new/changed fields appear in the HESA universe. | Alyson Shaw | 17/04/13 | PASS |
|
2.6 | Confirm that the new/changed fields appear in the HESA Archive universe. | Alyson Shaw | 17/04/13 | PASS |
Deliverable 1.2: Supporting data from PURE:
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
2.7-9 | Upload the csv data file from GaSP into the HR HESA Person table. Confirm that the new Research fields from the csv file appear in the HESA universe. | Alyson Shaw | 17/04/13 | N/A | This scenario is not quite valid. The csv file was loaded up at implementation time. It sits in a temp table but the hesa universe does not have a direct view on that table. However the new fields do show up in the universe along with the other fields we added to the extract table |
3. Deliverable 1.3: Changes to eRecruitment database, application, extract, and BOXI universe:
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
3.1 | Confirm that the new/changed SOC field appears in the eRecruitment application. |
|
|
| This is being done by HR systems team |
3.3 | Confirm that the new SOC values for records extracted from eRecruitment appear in the HR application. |
|
|
| This cannot be tested until all done in eRecruitment and we have test applicants set up |
3.4 | Confirm that the new SOC values appear in the eRecruitment universe. Note: Item removed because PPDR meeting agreed to pass this task to eRecruitment Phase 1B project. |
|
|
| N/A |
4. Deliverable 1.4: Changes to PPIPMI database and BOXI universe:
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
4.1 | Confirm that the new/changed fields appear in the PPIPMI universe. Note: PPIP de-scoped March 2013 |
|
|
| N/A |
5. Deliverable 2.1: Update the HESA extract facility for required final return functionality:
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
5.1 | Confirm that the new verstion of the HESA extract (to xml) has been deployed | Alyson Shaw | 17/04/13 | PASS |
|
6. Deliverable 2.2: Update the HESA submission method:
Reference (From BRD) | Scenario / Acceptance Criteria | Tested By | Date Tested | Outcome Pass/Fail | Notes |
6.1 | Confirm that all Staff fields appear in the HESA xml files | Alyson Shaw | 17/04/13 | PASS | On test many of the fields will be null because the new ACTSOC values have not been set against people’s records and this has knock on effects for population of other fields. where the fields are null they do not show in the xml and this means that after the first test run it looks as if ,any of them are missing.However for the purposes of integration testing I am satisfied that the overall process is working and detailed scenario testing can take place at UAT |
6.2 | Confirm that all Contract fields appear in the HESA xml files | Alyson Shaw | 17/04/13 | PASS | Same comment as above |
6.3 | Confirm that no Grades file is produced | Alyson Shaw | 17/04/13 | PASS |
|