T2-T2S Consolidation User Testing Terms of Reference (UT TOR)
Total Page:16
File Type:pdf, Size:1020Kb
ECB-PUBLIC July 2021 T2-T2S Consolidation User Testing Terms of Reference (UT TOR) Version Date Author Description Reviewed by 0.1 21/05/2021 ECB Draft MTRSG-DG 0.2 09/06/2021 ECB/4CB/MTSR Draft MTRSG-DG G-DG 0.3 11/06/2021 ECB Draft MTRSG/TSWG 0.4 28/06/2021 ECB Draft MTRSG/TSWG 0.5 08/07/2021 ECB Final MTRSG/TSWG/MIB Table 1: Document log t2_t2s_consolidation_user_testing_terms_of_reference.docxv0.5_external Page 1 of 30 ECB-PUBLIC Contents 1. Introduction 4 2. Test environments 5 2.1 General terms of reference 5 2.2 UTEST Operational day scheduling 5 2.3 Deployment management 7 2.4 Release Note 7 3. User Testing Reporting and Monitoring 7 3.1 Testing Calendar 8 4. Organisation of User Testing phases 9 4.1 Participating actors and UT phases 9 4.2 General Terms and assumptions 9 4.3 UT phases and timeline 12 4.4 UT – Connectivity Testing 13 4.4.1 Scope of the phase 13 4.4.2 Planning principles and timeline 13 4.5 Reference data setup for the UT 14 4.5.1 Registration Form submission 14 4.5.2 Subsequent reference data set-up - Community Approach 14 4.6 Reference Data Propagation 14 4.7 User Testing Community Testing phase 15 4.7.1 Scope of the phase 15 4.7.2 Planning principles and assumptions 16 4.8 User Testing Business day 16 4.8.1 Scope of the phase 16 4.8.2 Planning principles and assumptions 16 4.9 UT Mandatory Testing – T2 Mandatory test cases 17 5. Specific Tests – in parallel to User Testing phases 17 5.1 UT Operational Testing 17 5.2 Contingency Scenario Testing 18 5.3 Migration Testing 19 5.3.1 UT Migration weekend (dress) rehearsal 19 6. UT Entry/EXIT Criteria 19 6.1 Connectivity testing phase 19 6.2 User Testing Execution (UT Community and UT Business day phases) 20 7. Service Support during User Testing 21 t2_t2s_consolidation_user_testing_terms_of_reference.docx Page 2 of 30 ECB-PUBLIC In order to fully address the UT related aspects, the Eurosystem provides support to Central Banks via two interlocutors - the TARGET Service Desk and the ECB UT-MIG team. The National Service Desk at the Central Bank provides support to the T2 participants. 21 7.1 TARGET Service Desk 21 7.1.1 Responsibility 21 7.2 ECB UT-MIG team 21 7.2.1 Responsibility 22 7.3 NSD (National Service Desk) 22 7.3.1 Responsibility 22 7.3.2 Service Hours 22 8. Incident and defect management 23 8.1 Incident Management – National Service Desk 23 8.2 Defects 23 8.3 Consolidated List of open incidents and defects 24 9. Facilitating UT 25 9.1 Pre-Validation of messages 25 9.2 Testing simulators 25 9.2.1 General Terms and Workflow 25 9.3 Migration Testing tools 26 9.3.1 Migration of Balances Tool (MBT) 26 9.3.2 Data Migration Tool (DMT) 26 9.4 Facilitating Rehearsal 27 9.4.1 Summary document 27 9.4.2 Migration calls 27 9.4.3 Reporting 27 10. Glossary 28 t2_t2s_consolidation_user_testing_terms_of_reference.docx Page 3 of 30 ECB-PUBLIC 1. Introduction The User Testing Terms of Reference outlines the principles for the preparation, organisation and execution of User Testing, as agreed within the Eurosystem. This document covers all the aspects relevant for User Testing phase including the items relevant for the T2 Participants. This document consists of the following sections: Section 2 - Test Environment, which defines the principles and the scheduling for the usage of the test environment, processes of software deployment; Section 3 – User Testing Reporting and Monitoring which defines the responsibilities of the entities participating in the User Testing Stage and the regular monitoring aspects during the User Testing phase following the principles defined in T2 Testing Reporting Framework ; Section 4 - Organisation of Test Phases and the principles that apply for organising and executing test phases within User Testing Stage; Section 5 – Specific Tests – In parallel to User Testing phases, explains the additional testing activities to be carried out in parallel to the UT community and Business day testing phases Section 6 – UT Entry/Exit Criteria, which defines the general and any specific entry and/or exit criteria relevant for Connectivity and User Testing Stage; Section 7 - Service Support during User Testing, which defines the level of support that the Eurosystem (ECB UT-MIG team and the 4CB) will provide to the Central Banks during User Testing; Section 8 – Incident and defect Management during User Testing, which defines the workflow between the TARGET Service Desk and National Service Desk; Section 9 - Facilitating User Testing, which defines the terms, conditions and support that the Eurosystem will provide for the various types of User Testing. t2_t2s_consolidation_user_testing_terms_of_reference.docx Page 4 of 30 ECB-PUBLIC 2. Test environments UTEST will host the User Testing of the T2. In this context and for future references in this document, unless otherwise specified, T2 refers specifically to CLM and RTGS. 2.1 General terms of reference Within the timeframe defined for the User Testing, the Central Banks along with their community have the option to organise their testing activities with the User Testing phases provided that they support and respect the multilateral testing with other Central Banks (e.g. Migration testing, volume testing, contingency scenario, etc.) as agreed with their Central Banks . The scheduling of testing activities by a Central Bank and/or their participants must not impose a constraint on the testing of other system entity in the same Test Environment unless it has been agreed in advance within the all the involved testing entities. 2.2 UTEST Operational day scheduling • This section specifies the terms of reference for T2 operational day scheduling scenarios in UTEST as agreed and required for testing activities mentioned in the Testing Calendar. • Four (4) operational day schedules shall apply during the execution phase of User Testing with the exception of migration testing which follow the migration schedule/playbook. Operational day Description schedule T2 standard day Operational day schedule that T2 uses when a synchronisation of the scheduling between T2S and T2 is not required i.e. before the T2S services are connected to T2 in UTEST environment. T2-T2S synchronised Operational day schedule that T2 uses when a synchronisation of the standard day scheduling between T2S and T2 is required i.e. after the T2S services are connected to T2 in UTEST environment. T2-T2S synchronised Operational day schedule that T2 uses in UTEST environment for a release day day in which the deployment of a bug fix release. T2 Live Timing Operational day schedule that operates on the same timings as the Schedule production environment during the Business day testing stage in UTEST environment. t2_t2s_consolidation_user_testing_terms_of_reference.docx Page 5 of 30 ECB-PUBLIC • Once the TARGET Services T2S, TIPS1 and T2 are inter-connected, the scheduling of these TARGET services will be aligned. • The UTEST test environment will be available during the standard opening hours (07:00 and 19:00 CET) from Monday to Friday except o for 1 January, Catholic/Protestant Good Friday, Easter Monday, 1 May (Labour Day), 24 December, 25 December (Christmas Day), 26 December, 31 December o when any maintenance activities are scheduled and o when a deployment of software release has been agreed • The T2 Standard Day will apply as default to the UTEST test environment from Monday to Thursday until the TARGET services are connected and the T2-T2S synchronised schedule shall apply when all the TARGET services are connected during the User Testing phase. • On Fridays, by default T2-T2S Synchronised Release day schedule will be applied in the UTEST environment, whether or not a deployment is planned. • The scheduling for Migration testing will follow the community approach (refer section 4.3.2) for reference data set-up, and Migration Weekend Playbook when Migration Weekend Rehearsal testing takes place. The specific requirements and scope of the migration testing will determine the processes and procedures of the Migration Weekend Playbook. • No UTEST operational day scheduling scenario will require extended operational and technical support outside the support hours (for further details on Service Hours – see Section 7). If a problem occurs during the night, the TARGET Operator will address the disturbance at the beginning of the next business day (i.e. 7.00 when the service hours starts) with a possible delay of the start of the normal operations and informs the TARGET Service Desk. The TARGET Service will communicate the details of the issue and when in position, also provides the way forward to handle the issue under analysis. The Target Service Desk provides/communicates such information only to the Central Banks and the Central Banks convey the relevant information to the T2 Participants. • The detailed schedule for each Operational day schedule shall be provided 3 months before the start of User Testing execution phase and will be added as an annex to this deliverable. 1 TIPS do not have separate schedule, it follows T2 schedule t2_t2s_consolidation_user_testing_terms_of_reference.docx Page 6 of 30 ECB-PUBLIC 2.3 Deployment management Deployment management organises the rollout of software releases and/or configurable parameter changes to UTEST. During the UT, all deployment activities will be included in the testing calendar. 2.4 Release Note All changes in the T2, including the common components in UTEST (incl. bug-fixing changes) are clearly documented and provided by the 4CB in a release note before deployment. The contents will include the defect number and a brief description of the issue, while the specific details are provided in the PBI (e.g.