User Acceptance Testing
Acceptance Test Strategy
Scheduling and duration:
The original plan was as follows:
UAT start date Monday 25th November.
Three weeks of initial UAT testing, to be completed by Friday 13th December.
Two weeks of re-testing addressed feedback, w/c Monday 18th December and w/c Monday 5th January.
Target date for UAT sign-off is Friday 9th January.
However, at the Business Analysis Review meeting, the Project Sponsor asked that the project be re-planned to deliver the Phase 2 functionality in batches. This section will be updated to reflect the results of that re-planning, when they become available.
Test environment setup requirements:
Build to be Integrated to Test and Integration Tested prior to the start of UAT.
Sources of test data:
The Test environment will be refreshed from Live eAuthorisations prior to the start of UAT.
Subsequent data will be keyed in by testers.
Test scripts
To be provid:ed by the Finance Business Testing Coordinator
Responsibilities for testing:
The ISA Team is responsible for setting up the Test environment, and ensuring that the system has been successfully Integrated prior to the start of UAT testing.
Finance Business Testing Coordinator is responsible for forming the UAT testing team, coordinating the testing feedback, raising Jiras for approved feedback, assigning Jiras to the ISA team to be addressed, and coordinating the re-testing and sign-off of each Jira. Feedback coordination must be handled responsively, and as swiftly as possible.
Other test participants and any training requirements:
Participants to be identified by the Finance Business Testing Coordinator.
Training requirements to be identified by the Finance Business Testing Coordinator.
Technical and business support required during testing:
The ISA team will be resourced to support the UAT testers, and to address testing feedback.
The Business team must have their testing responsibilities prioritised by Finance managers, to avoid unnecessary delays in the sign-off and deployment.
Communication requirements:
Feeback to be swiftly turned around into Jiras and assigned to the ISA team.
Addressed Jiras will be assigned back to the Finance Business Testing Coordinator for re-testing and closure.
Test Scenarios and Acceptance Criteria
Requirements for Deliverable 3 | Ref | Scenario / Acceptance Criteria | Responsibility for Testing |
Upgrade ColdFusion code to Mach-ii framework | D3.1 | Regression testing required. Details to be provided by Finance Business Testing Coordinator | Finance |
Provide fail-over and fail-back resilience in Live environment | D3.2 | Regression testing required. Details to be provided by Finance Business Testing Coordinator | Finance |
Perform system Load testing, using the criteria agreed with Finance (see specified requirements ) | D3.3 | Details to be provided by Finance Business Testing Coordinator | Finance |
The downstream export mechanism must be made more robust. At present there is no failure handling, which causes data mismatch between eAuthorisations and the downstream system (Jiras FIN089-13 and FIN089-12). | D3.4.1 | Details to be provided by Finance Business Testing Coordinator | Finance |
Pre-existing issue: There is a bug with the eStores user upload utility on IE (Jira FIN089-16) | D3.4.2 | Details to be provided by Finance Business Testing Coordinator | Finance |
Pre-existing issue: Changing staff UUN does not use Central Auth validation (Jira FIN089-14). | D3.4.3 | Details to be provided by Finance Business Testing Coordinator | Finance |
| Add a link to the new ABS-supplied validation routine for cost centre / account code / job code combinations (Jira FIN089-20, added by project FIN079) | D3.5 | Details to be provided by Finance Business Testing Coordinator | Finance |
| Prevent the loading of two separate records for a single UUN | D3.6.1 | Details to be provided by Finance Business Testing Coordinator | Finance |
Run a one-off check against the database to identify all duplicates (two records with same UUN) | D3.6.2 | Details to be provided by Finance Business Testing Coordinator | Finance |
| Resolve issue with common (shared) codes at College level not being picked up | D3.6.3 | Details to be provided by Finance Business Testing Coordinator | Finance |
Improve the appearance and functionality of the application
| D3.6.4 | Details to be provided by Finance Business Testing Coordinator | Finance |
Add email notifications to FISUSERS:
| D3.6.5 | Details to be provided by Finance Business Testing Coordinator | Finance |
Requirements for Deliverable 4 | Ref | Scenario / Acceptance Criteria | Responsibility for Testing |
Add functionality to allow FIS staff to manage Transaction Type LoV:
| D4.1.1 | Details to be provided by Finance Business Testing Coordinator | Finance |
Add functionality to allow FIS staff to manage Every other LoV currently available within eAuthorisations:
Every LoV should allow alphanumeric entries. No validation to be performed, so that FIS can apply any value to any LoV entry. | D4.1.2 | Details to be provided by Finance Business Testing Coordinator | Finance |
Admin functionality to apply LoV values to individuals For every LoV currently available within eAuthorisations
| D4.1.3 | Details to be provided by Finance Business Testing Coordinator | Finance |
| Create a basic BOXI universe against the eAuthorisations database. Include the database tables and links identified in the Entity Relationship Model (secure). Finance have confirmed that a simple design approach should be used, i.e.:
| D4.2 | Details to be provided by Finance Business Testing Coordinator | Finance |