Common use of TEST STRATEGY Clause in Contracts

TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable after the Lease Agreement Commencement Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree) after the Lease Agreement Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in relation to the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the procedure to be followed should a Deliverable fail a Test, fail to satisfy the Test Success Criteria or where the Testing of a Deliverable produces unexpected results, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; the process for the production and maintenance of Test Reports, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues the names and contact details of the Customer's and the Supplier's Test representatives; a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and reports relating to such personnel, and Customer and/or third party involvement in the conduct of the Tests; the technical environments required to support the Tests; and the procedure for managing the configuration of the Test environments. The Supplier shall develop Test Plans and submit these for Approval as soon as practicable but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise) prior to the start date for the relevant Testing as specified in the Implementation Plan. Each Test Plan shall include as a minimum: the relevant Test definition and the purpose of the Test, the Milestone to which it relates, the requirements being Tested and, for each Test, the specific Test Success Criteria to be satisfied; a detailed procedure for the Tests to be carried out, including: the relevant Test Issue Thresholds; the timetable for the Tests including start and end dates; the Testing mechanism; dates and methods by which the Customer can inspect Test results or witness the Tests in order to establish that the Test Success Criteria have been met; the mechanism for ensuring the quality, completeness and relevance of the Tests; the format and an example of Test progress reports and the process with which the Customer accesses daily Test schedules; the process which the Customer will use to review Test Issues and the Supplier’s progress in resolving these on a timely basis; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; and the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the Test Issue. The Customer shall not unreasonably withhold or delay its approval of the Test Plan provided that the Supplier shall implement any reasonable requirements of the Customer in the Test Plan.

TEST STRATEGY. 2.1 The Supplier Prime DSP shall develop and maintain the final Test Strategy as soon as practicable after that shall describe, at a high-level, the Lease Agreement Commencement Date but Testing strategy and arrangements applicable to each and every testing activity to be conducted by the Prime DSP and each testing activity to be conducted by each Prime CSP in any case no later than twenty connection with their respective DCC Service Provider Contract (20) Working Days (or such other period as the Parties may agree) after the Lease Agreement Commencement Dateincluding in connection with Enduring Testing). The final Contractor shall ensure the Test Strategy relates to all Test Activities in the applicable Test Phases and complies with all Test Requirements and DCC Requirements. The Contractor shall ensure the Test Strategy contains a V-model diagram that details the relationship of the design baseline (including Contractor Solution Design Documents and Service Management Framework documents (and equivalents of any such documents prepared by each Prime CSP) and relevant Communications Hub design documents) to the Test Stages. 2.2 The Contractor shall review and update the Test Strategy so as to ensure that it is kept fully up-to-date and accurately reflects the status of Testing. 2.3 The Contractor shall provide copies of the Test Strategy to the DCC promptly on request from time to time. 2.4 The Test Strategy shall include: : (a) an overview of each Test Phase and Test Stage; (b) an overview of how Testing will be conducted conducted; (c) the Testing procedure including details, amongst other things, of the scope of each Test Phase in relation to accordance with the Implementation Plan; Test Requirements; (d) the process to be used to capture and record Test results and the categorisation of Test Issues; Incidents; (e) the method for mapping the expected Test results to the Test Success Criteria; (f) the procedure to be followed should a Deliverable fail a Test, fail to satisfy the Test Success Criteria not be met or where the Testing of a Deliverable produces unexpected resultsTest results fail to be as expected or any Stage Exit Criteria not be met, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; any rectification procedure; (g) the process for the production and maintenance of Test ReportsReports and reporting, including (if applicable) templates for the Test Reports and the Contractor’s Test Issue Incident Management Log (or where appropriate the Prime DSP's Test Incident Management Log), and a sample plan for the resolution of to resolve Test Issues Incidents; (h) the names and contact details of the Customer's DCC’s representatives (if applicable), relevant Other Service Providers' representatives and the Supplier's Contractor’s Test representatives; ; (i) a high level identification of the resources required for Testing, including facilities, infrastructure, Test Stubs, Smart Metering Devices and other equipment, personnel and reports relating to such personnel, and Customer DCC and/or third party involvement in support for the conduct of the Tests; ; (j) for the User Integration Test Phase and Enduring Testing a high level identification of the Prime DSP and Prime CSP resources required for DCC and DCC Service Users to plan and execute their testing and to support the analysis and resolution of Test Incidents; (k) for all Test Phases, the extent of functional and non-functional testing; (l) all high-level dependencies (including any DCC Responsibilities) for the applicable Phase; (m) the technical environments required to support the Tests; and and (n) the procedure for managing the configuration of the Test environments. The Supplier shall develop Test Plans and submit these for Approval as soon as practicable but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise) prior to the start date for the relevant Testing as specified in the Implementation Plan. Each Test Plan shall include as a minimum: the relevant Test definition and the purpose of the Test, the Milestone to which it relates, the requirements being Tested and, for each Test, the specific Test Success Criteria to be satisfied; a detailed procedure for the Tests to be carried out, including: the relevant Test Issue Thresholds; the timetable for the Tests including start and end dates; the Testing mechanism; dates and methods by which the Customer can inspect Test results or witness the Tests in order to establish that the Test Success Criteria have been met; the mechanism for ensuring the quality, completeness and relevance of the Tests; the format and an example sourcing of Test progress reports and Data (including confirmation of agreement from the process with which sourcing party where this is not the Customer accesses daily Test schedules; the process which the Customer will use to review Test Issues and the Supplier’s progress in resolving these on a timely basis; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; and the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the Test Issue. The Customer shall not unreasonably withhold or delay its approval of the Test Plan provided that the Supplier shall implement any reasonable requirements of the Customer in the Test PlanPrime DSP).

TEST STRATEGY. 3.1 The Supplier Service Provider shall develop ensure that the final Test Strategy as soon as practicable after includes at least the Lease Agreement Commencement Date but in any case no later than twenty following: (20A) Working Days (or such other period as the Parties may agree) after the Lease Agreement Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in relation to the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the procedure to be followed should a Deliverable fail a Test, fail to satisfy the Test Success Criteria or where overall plan for the Testing of the Enforcement System, the CSP Interface, and the Services which shall comply with paragraph 5 of this schedule; (B) a Deliverable produces unexpected resultsbrief description of the approach to Testing during the Implementation Phase and after the Operational Commencement Date, including a procedure the rationale for the resolution of Test Issues; the procedure to be followed to sign off each Test; the process for the production and maintenance of Test Reports, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues such approach; (C) the names and contact details of the CustomerService Provider's and representatives for the Supplier's Test representatives; a high level identification purposes of the resources required for Testing; (D) the requirements and objectives of the Testing; (E) any dependencies affecting the Testing, including facilities, infrastructure, personnel and reports relating to such personnel, and Customer and/or reliance on third party involvement in parties; (F) the conduct scope of the Tests; Testing; (G) any assumptions made that may impact upon Testing; (H) the technical environments required perceived risks to support the Tests; Testing or risks, Service Issues or other issues as a result of Testing together with their impact and the procedure for managing the configuration methods of mitigation; (I) descriptions of the Test environments. The Supplier shall develop Test Plans stages of Testing including without limitation the processes for establishing and submit these for Approval as soon as practicable but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise) prior to the start date for the relevant Testing as specified in the Implementation Plan. Each Test Plan shall include as a minimum: implementing the relevant Test definition Specification against which the Testing will be conducted and assessed; (J) descriptions of the anticipated processes relating to Testing for achieving a Notice of Authority to Proceed in respect of each relevant Milestone including the performance of the Service Provider’s obligations in respect of Test Witnessing, Test Reports, Incident management and the purpose of the Test, the Milestone to which it relates, the requirements being Tested and, for each Test, the specific Test Success Criteria business process scenarios to be satisfied; a detailed procedure for the Tests to be carried out, including: the relevant Test Issue Thresholds; the timetable for the Tests including start and end dates; the Testing mechanism; dates and methods by which the Customer can inspect Test results or witness the Tests used in order to establish that determining whether the Test Success Criteria have been met; (K) the entry and exit criteria applicable to the Testing; Schedule 4 – Testing Regime (L) the mechanism for ensuring roles and responsibilities of all those involved with the qualityTesting programme, completeness and relevance including the Service Provider’s Personnel or personnel of TfL and/or third parties where applicable; (M) an outline of the Testsresource requirements, including Personnel, Personnel training, test environments, and Testing tools; and how they will be used during Testing; (N) the format location of the Testing; (O) the sources and an example mechanisms for creation of Test progress reports and Data for use during Testing; (P) a description of the process with which the Customer accesses daily Test schedules; the process which the Customer steps that will use be taken to review Test Issues and the Supplier’s progress in resolving these on a timely basis; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; and the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve secure the Test Issue. The Customer shall not unreasonably withhold or delay its approval of Data, to process it in compliance with data protection laws, and to delete it securely; (Q) the quality management tools and processes to be used in Testing including: (1) any standards to be applied to Testing; (2) Incident and problem management processes; (3) Test Plan provided that the Supplier shall implement any reasonable requirements of the Customer in the results capture, logging, and tracking; and (4) Test Planprogress and completion reporting.

TEST STRATEGY. 3.1 The Supplier shall develop Service Provider shall, in accordance with Schedule 3 (Milestones and Deliverables), prepare and submit to TTL a Test Strategy. As a minimum, the final Test Strategy as soon as practicable after the Lease Agreement Commencement Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree) after the Lease Agreement Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in relation to the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the procedure to be followed should : (A) a Deliverable fail a Test, fail to satisfy the Test Success Criteria or where high level plan for the Testing of a Deliverable produces unexpected resultsthe LCHS Assets and Service Systems, including a procedure for the resolution scheduling of Test Issues; the procedure all Tests to be followed completed during the Implementation Phase; (B) a description and rationale of the approach to sign off each TestTesting during the: (1) Implementation Phase; the process for the production and maintenance of Test Reports, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues and (2) Operational Phase; (C) the names and contact details of the CustomerTTL's and the SupplierService Provider's Test representatives; a high level identification Representatives responsible for Testing; (D) the requirements and objectives of the resources required for Testing; (E) any dependencies affecting the Testing, including facilitiesreliance on Interested Parties, infrastructureOther Service Providers, personnel the Insurance Provider and reports relating to such personnel, and Customer and/or third party involvement in Third Parties; (F) the conduct scope of the Tests; Testing; (G) any assumptions made by the technical environments required Service Provider that may impact upon Testing; (H) the perceived risks to support the Tests; Testing, Service Issues or other risks and the procedure for managing the configuration issues as a result of Testing together with their impact and methods of mitigation; (I) descriptions of the Test environments. The Supplier shall develop Test Plans stages of Testing, including the processes for establishing and submit these for Approval as soon as practicable but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise) prior to the start date for the relevant Testing as specified in the Implementation Plan. Each Test Plan shall include as a minimum: implementing the relevant Test definition Specification against which the Testing will be conducted and the purpose assessed; (J) descriptions of the Testanticipated processes relating to Testing for achieving a Milestone Notice, including: (1) the Milestone to which it relates, performance of the requirements being Tested Service Provider‟s obligations in respect of: (a) Test Witnessing; (b) Test Reports; and, for each Test, (c) Incident management; and (2) the specific Test Success Criteria business process scenarios to be satisfied; a detailed procedure for the Tests to be carried out, including: the relevant Test Issue Thresholds; the timetable for the Tests including start and end dates; the Testing mechanism; dates and methods by which the Customer can inspect Test results or witness the Tests used in order to establish that determining whether the Test Success Criteria have been met; ; (K) the mechanism for ensuring the quality, completeness entry and relevance of the Tests; the format and an example of Test progress reports and the process with which the Customer accesses daily Test schedules; the process which the Customer will use exit criteria applicable to review Test Issues and the Supplier’s progress in resolving these on a timely basis; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; and the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the Test Issue. The Customer shall not unreasonably withhold or delay its approval each of the Test Plan provided that Stages; (L) the Supplier shall implement any reasonable requirements roles and responsibilities of all those involved with the Testing programme, including TTL Personnel, Service Provider Personnel and/or personnel of Interested Parties, Other Service Providers, the Insurance Provider and Third Parties where applicable; (M) an outline of the Customer in resource requirements, including TTL Personnel, Service Provider Personnel and/or personnel of Interested Parties, Other Service Providers, the Insurance Provider and Third Parties, training of such personnel, Test Environments, and Testing tools and how such resources will be used during each Test Stage; (N) the location of the Testing at each Test Stage; (O) the sources and mechanisms for creation of Test Data for use at each Test Stage; (P) a description of the steps that will be taken to: (1) secure the Test Data; (2) process Test Data in compliance with Data Protection Legislation; and (3) to delete Test Data securely; (Q) a proposed process for acceptance of: (1) relevant LCHS Assets; and (2) new versions and/or releases of Service Systems for production use, during the Operational Phase; (R) the quality management tools and processes to be used in Testing, including: (1) the standards to be applied to Testing; (2) requirement traceability mechanisms, based on the “Standard Glossary of terms used in Software Testing”, V1.3 produced by the International Software Testing Quality Board (ISTQB): Requirements Traceability Mechanism that provides the ability to identify requirements with related items in Documentation and Software, in particular, identifying requirements with associated Tests; (3) Incident and Problem management processes; (4) configuration management; (5) release management; (6) capture, logging, and tracking of Test results; and (7) Test progress and completion reporting; and (S) each of the foregoing in respect of the: (1) Business Continuity Test Schedule and Testing of the Business Continuity Plan; and (2) Business Continuity Infrastructure and Business Continuity Services.

TEST STRATEGY. 2.1 The Supplier Prime DSP shall develop and maintain the final Test Strategy as soon as practicable after that shall describe, at a high-level, the Lease Agreement Commencement Date but Testing strategy and arrangements applicable to each and every testing activity to be conducted by the Prime DSP and each testing activity to be conducted by each Prime CSP in any case no later than twenty connection with their respective DCC Service Provider Contract (20) Working Days (or such other period as including in connection with Enduring Testing). 2.2 Not used. 2.3 The Contractor shall provide copies of the Parties may agree) after the Lease Agreement Commencement Date. The final Test Strategy shall to the DCC promptly on request from time to time. 2.4 The Test Strategy developed by the Prime DSP is expected to include: : (a) an overview of each Test Phase and Test Stage; (b) an overview of how Testing will be conducted conducted; (c) the Testing procedure including details, amongst other things, of the scope of each Test Phase in relation to accordance with the Implementation Plan; Test Requirements; (d) the process to be used to capture and record Test results and the categorisation of Test Issues; Incidents; (e) the method for mapping the expected Test results to the Test Success Criteria; (f) the procedure to be followed should a Deliverable fail a Test, fail to satisfy the Test Success Criteria not be met or where the Testing of a Deliverable produces unexpected resultsTest results fail to be as expected or any Stage Exit Criteria not be met, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; any rectification procedure; (g) the process for the production and maintenance of Test ReportsReports and reporting, including (if applicable) templates for the Test Reports and the Contractor’s Test Issue Incident Management Log (or where appropriate the Prime DSP's Test Incident Management Log), and a sample plan for the resolution of to resolve Test Issues Incidents; (h) the names and contact details of the Customer's DCC’s representatives (if applicable), relevant Other Service Providers' representatives and the Supplier's Contractor’s Test representatives; ; (i) a high level identification of the resources required for Testing, including facilities, infrastructure, Test Stubs, Smart Metering Devices and other equipment, personnel and reports relating to such personnel, and Customer DCC and/or third party involvement in support for the conduct of the Tests; ; (j) for the User Integration Test Phase and Enduring Testing a high level identification of the Prime DSP and Prime CSP resources required for DCC and DCC Service Users to plan and execute their testing and to support the analysis and resolution of Test Incidents; (k) for all Test Phases, the extent of functional and non-functional testing; (l) all high-level dependencies (including any DCC Responsibilities) for the applicable Phase; (m) the technical environments required to support the Tests; and and (n) the procedure for managing the configuration of the Test environments. The Supplier shall develop Test Plans and submit these for Approval as soon as practicable but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise) prior to the start date for the relevant Testing as specified in the Implementation Plan. Each Test Plan shall include as a minimum: the relevant Test definition and the purpose of the Test, the Milestone to which it relates, the requirements being Tested and, for each Test, the specific Test Success Criteria to be satisfied; a detailed procedure for the Tests to be carried out, including: the relevant Test Issue Thresholds; the timetable for the Tests including start and end dates; the Testing mechanism; dates and methods by which the Customer can inspect Test results or witness the Tests in order to establish that the Test Success Criteria have been met; the mechanism for ensuring the quality, completeness and relevance of the Tests; the format and an example sourcing of Test progress reports and Data (including confirmation of agreement from the process with which sourcing party where this is not the Customer accesses daily Test schedules; the process which the Customer will use to review Test Issues and the Supplier’s progress in resolving these on a timely basis; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; and the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the Test Issue. The Customer shall not unreasonably withhold or delay its approval of the Test Plan provided that the Supplier shall implement any reasonable requirements of the Customer in the Test PlanPrime DSP).