Common use of TEST PLANS Clause in Contracts

TEST PLANS. The Service Provider shall develop Test Plans and submit these for the approval of the Purchaser 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 agree in writing) prior to the start date for the relevant Testing (as specified in the Implementation Plan). The Purchaser shall define any additional Tests to be included in the Test Plan for the approval of the Service Provider, such approval not to be unreasonably withheld or delayed. 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 (agreed by both Parties) to be satisfied; a detailed procedure for the Tests to be carried out, including: the timetable for the Tests, including start and end dates; the Testing mechanism, including relevant tools and techniques being used; dates and methods by which the Purchaser can execute its own Tests (where relevant), 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 Purchaser accesses daily Test schedules; the process which the Purchaser will use to review Test Issues and the Service Provider’s progress in resolving these in a timely basis; the Test schedule; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the Test Issue. The Purchaser shall not unreasonably withhold or delay its approval of the Test Plans provided that the Service Provider shall incorporate any reasonable requirements of the Purchaser in the Test Plans. The Test Success Criteria for the Milestone Achievement Certificates have been agreed by the Parties prior to the Commencement Date and are set out in Annex 4 to this Schedule. For each phase of the Implementation Period, the Test Success Criteria for: each Test that the Service Provider must Achieve for the ATP Milestone or a Contract Performance Point (“CPP”) Milestone, are set out in Annex 4; and all other Tests shall be agreed between the Parties as part of the relevant Test Plan pursuant to paragraph 5. Following approval of a Test Plan, the Service Provider shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan. Each Test Specification shall include as a minimum: a mechanism for tracking traceability of Tests being conducted to requirements; the specification of the Test data, including its source, scope, volume and management, a request (if applicable) for relevant Test data to be provided by the Purchaser and the extent to which it is equivalent to live operational data; a plan to make the resources available for Testing; Test scripts; Test pre-requisites and the mechanism for measuring them; and expected Test results, including: a mechanism to be used to capture and record Test results; and a method to process the Test results to establish their content.

TEST PLANS. The Service Provider Supplier shall develop Test Plans and submit these for the approval of the Purchaser 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 agree in writingotherwise) prior to the start date for the relevant Testing (as specified in the Implementation Plan). The Purchaser shall define any additional Tests to be included in the Test Plan for the approval of the Service Provider, such approval not to be unreasonably withheld or delayed. 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 Tested and, for each Test, the specific Test Success Criteria (agreed by both Parties) to be satisfied; a detailed procedure for the Tests to be carried out, including: the relevant Test Issue Thresholds; the timetable for the Tests, Tests including start and end dates; the Testing mechanism, including relevant tools and techniques being used; dates and methods by which the Purchaser Customer can execute its own Tests (where relevant), 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 Purchaser Customer accesses daily Test schedules; the process which the Purchaser Customer will use to review Test Issues and the Service ProviderSupplier’s progress in resolving these in on a timely basis; the Test schedule; 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 Purchaser Customer shall not unreasonably withhold or delay its approval of the Test Plans Plan provided that the Service Provider Supplier shall incorporate implement any reasonable requirements of the Purchaser Customer in the Test Plans. The Test Success Criteria for the Milestone Achievement Certificates have been agreed by the Parties prior to the Commencement Date and are set out in Annex 4 to this Schedule. For each phase of the Implementation Period, the Test Success Criteria for: each Test that the Service Provider must Achieve for the ATP Milestone or a Contract Performance Point (“CPP”) Milestone, are set out in Annex 4; and all other Tests shall be agreed between the Parties as part of the relevant Test Plan pursuant to paragraph 5. Following approval of a Test Plan, the Service Provider shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan. Each Test Specification shall include as a minimum: a mechanism for tracking traceability of Tests being conducted to requirements; the specification of the Test data, including its source, scope, volume and management, a request (if applicable) for relevant Test data to be provided by the Purchaser and the extent to which it is equivalent to live operational data; a plan to make the resources available for Testing; Test scripts; Test pre-requisites and the mechanism for measuring them; and expected Test results, including: a mechanism to be used to capture and record Test results; and a method to process the Test results to establish their content.

TEST PLANS. 4.1 The Service Provider Contactor shall develop and maintain the Test Plans and submit these for the approval each Test Stage identified at paragraph 1.5 of the Purchaser 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 this Part B. The Contractor shall ensure all Test Plans that are Contractor's Test Documents comply with the Test Strategy or otherwise agree in writing) prior to the start date for the and relevant Testing (as specified in the Implementation Plan)Test Approach. The Purchaser Contractor shall define any additional Tests to be included in the Test Plan for the approval of the Service Provider, ensure each such approval not to be unreasonably withheld or delayed. Each Test Plan shall include include, as a minimum: , the relevant details set out below in relation to the applicable Test definition and the purpose Stage: (a) details of the TestTesting, the Milestone confirmation of any applicable Milestones to which it relatesthe Testing may relate, the requirements being tested Tested and, for each Test, the specific Test Success Criteria (agreed by both Parties) to be satisfied; met; (b) a detailed procedure for the Tests to be carried out, including: : (i) the timetable for the Tests, Tests including start and end dates; dates (in accordance with this Agreement and any applicable Implementation Plan); (ii) a full list of the Testing mechanism, including relevant tools and techniques being used; Test Specifications applicable to each Test Stage; (iii) dates and methods by which the Purchaser DCC can execute its own Tests (where relevant), inspect Test results or witness the Tests in order to establish that the applicable Stage Exit Criteria and Test Success Criteria have been met; ; (iv) dates agreed with the DCC to allow them to conduct identified acceptance activities; (v) the mechanism for ensuring the quality, completeness and relevance of the Tests; ; (vi) the format and an example of Test progress reports and the process with which the Purchaser DCC accesses daily Test schedules; ; (vii) the process with which the Purchaser DCC will use to review Test Issues Incidents and the Service Provider’s progress in resolving these in on a timely basis; ; (viii) the Test schedule; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; the process for escalating Test Issues from a re-test situation to the taking schedule of specific remedial action to resolve the Test Issue. The Purchaser shall not unreasonably withhold or delay its approval of the Test Plans provided that the Service Provider shall incorporate any reasonable requirements of the Purchaser in the Test Plans. The Test Success Criteria for the Milestone Achievement Certificates have been agreed by the Parties prior to the Commencement Date and are set out in Annex 4 to this Schedule. For each phase of the Implementation Period, the Test Success Criteria for: each Test that the Service Provider must Achieve for the ATP Milestone or a Contract Performance Point Tests; (“CPP”ix) Milestone, are set out in Annex 4; and all other Tests shall be agreed between the Parties as part of the relevant Test Plan pursuant to paragraph 5. Following approval of a Test Plan, the Service Provider shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan. Each Test Specification shall include as a minimum: a mechanism for tracking traceability of Tests being conducted to requirements; the specification of the Test dataData, including its source, scope, volume and management, a request (if applicable) for relevant Test data Data to be provided by another person (which may include the Purchaser DCC acting on behalf of the DCC Service Users) with agreed dates at which it shall be provided and the extent to which it is equivalent to live operational data; ; (x) the information required by paragraph 5.1(c) (under the heading Test Data) of Part C (Testing); (xi) a plan to make the resources available for Testing; Testing including any environments, Test scripts; Labs, facilities, model offices, infrastructure, Test prepersonnel, third party and/or DCC involvement; (xii) the re-requisites Test procedure, the timetable and the mechanism resources which would be required for measuring themre-Testing; (xiii) a Traceability Matrix to map Test Specifications to DCC Requirements; and (xiv) the decision making process for escalation from a re-test situation to specific remedial action to resolve the problem / Test Incident. 4.2 The Contractor shall review and expected at all times keep up-to-date (in accordance with the process described in paragraph 6 of this Part B of this Schedule 6.2) each Test results, including: a mechanism Plan it was required to be used develop and maintain in accordance with this Agreement so as to capture ensure that they are kept fully up-to-date and record Test results; accurately reflect the then current status of the relevant Testing Activities (including any arrangements in connection with Future Testing Activities) and a method otherwise continue to process comply with the Test results to establish their contentrequirements of this Schedule 6.2.

TEST PLANS. The Service Provider Supplier shall develop Test Plans and where requested submit these for review by the approval of the Purchaser Authority as soon as practicable but in any case no later than twenty (20) Working Days following the Effective Date (or such other period as by any deadline agreed between the Parties may agree parties in the Test Strategy Agreed Transition Milestone Plan, or otherwise agree in writing) prior to the start date for the relevant Testing (as specified in the Implementation Planotherwise). The Purchaser shall define any additional Tests to be included in the Test Plan for the approval of the Service Provider, such approval not to be unreasonably withheld or delayed. Each Test Plan shall include as a minimum: the relevant Test or check definition and the purpose of the Test, the Milestone to which it relates, the requirements being tested Test or check and, for each Test, the specific Test Success Criteria (agreed by both Parties) and/or Workshop Readiness Success Criteria to be satisfied; a detailed procedure for the Tests and checks to be carried out, including: the timetable for the TestsTests and checks, including start and end dates; the Testing mechanism, including relevant tools and techniques being used; dates and methods by which the Purchaser can execute its own Tests (where relevant), Authority can/may wish to inspect Test or check results or witness the Tests or check in order to establish that the Test Success Criteria and/or Workshop Readiness 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 Purchaser accesses daily Test schedules; the process which the Purchaser will use to review Test Issues and the Service Provider’s progress in resolving these in a timely basis; the Test schedule; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; the process for escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the Test Issue. The Purchaser shall not unreasonably withhold Tests or delay its approval of the Test Plans provided that the Service Provider shall incorporate any reasonable requirements of the Purchaser in the Test Planschecks. The Test Success Criteria for each Test shall be as set out in the Milestone Achievement Certificates Test Plan. The Workshop Readiness Success Criteria for each Retail Workshop will be that the Supplier can demonstrate to the reasonable satisfaction of the Authority that all the relevant requirements of the Workshop Readiness Check List have been agreed by fulfilled and that the Parties prior Retail Workshop is ready to deliver the provisions of the Retail Services as described in the Services Description set out in Schedule 2.1. Once the Supplier has: successfully completed and met the Test Success Criteria for any Test conducted in accordance with this Schedule 6.2 (Workshop Readiness Check); and successfully completed the Workshop Readiness Check in accordance with this Schedule 6.2 (Workshop Readiness Check), it shall issue to the Commencement Date and are Authority, the Workshop Readiness Notice in the form set out in Annex 4 to this ScheduleA along with any Test Reports or other information as the Authority may reasonably request in respect of any Test or Workshop Readiness Check. For each phase On receipt of the Implementation PeriodWorkshop Readiness Notice, the Authority may either: conduct a Test Success Criteria for: each Test Quality Audit; request additional information from the Supplier in respect of the readiness of the Workshop for the commencement of Operational Services Commencement; or Approve the Workshop Readiness Checklist and confirm that the Service Provider must Achieve for relevant Milestone has been Achieved. Without prejudice to its rights pursuant to Schedule 7.5 (Financial Reports and Audit Rights) and Schedule 8.4 (Reports and Records Provision), the ATP Milestone or a Contract Performance Point (“CPP”) Milestone, are set out Authority may perform on-going quality audits in Annex 4; and all other Tests shall be agreed between the Parties as respect of any part of the relevant Test Plan pursuant to paragraph 5and the Workshop Readiness Check. Following approval If the Testing Quality Audit gives the Authority concern in respect of a the Testing Procedures or any Test Planor the Workshop Readiness Checklist, the Service Provider shall develop Authority shall: discuss the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start outcome of the relevant Testing (as specified in Quality Audit with the Implementation Plan. Each Test Specification shall include as a minimum: a mechanism for tracking traceability of Tests being conducted to requirements; the specification of the Test dataSupplier, including its source, scope, volume and management, a request (if applicable) for relevant Test data to be provided by the Purchaser and the extent to which it is equivalent to live operational data; a plan to make the resources available for Testing; Test scripts; Test pre-requisites and the mechanism for measuring them; and expected Test results, including: a mechanism to be used to capture and record Test results; and a method to process the Test results to establish their content.giving the

TEST PLANS. The Service Provider Supplier shall develop Test Plans and submit these for the approval of the Purchaser Authority as soon as practicable but in any case no later than twenty (20) 20 Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start date for the relevant Testing (as specified in the Implementation Plan). The Purchaser shall define any additional Tests to be included in the Test Plan for the approval of the Service Provider, such approval not to be unreasonably withheld or delayed. 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 (agreed by both Parties) to be satisfied; a detailed procedure for the Tests to be carried out, including: the timetable for the Tests, including start and end dates; the Testing mechanism, including relevant tools and techniques being used; dates and methods by which the Purchaser Authority can execute its own Tests (where relevant), 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 Purchaser Authority accesses daily Test schedules; the process which the Purchaser Authority will use to review Test Issues and the Service Provider’s Supplier's progress in resolving these in a timely basis; the Test schedule; and the re-Test re‑Test procedure, the timetable and the resources which would be required for re-Testingre‑Testing; and the process for escalating Test Issues from a re-test re‑test situation to the taking of specific remedial action to resolve the Test Issue. The Purchaser Authority shall not unreasonably withhold or delay its approval of the Test Plans provided that the Service Provider Supplier shall incorporate any reasonable requirements of the Purchaser Authority in the Test Plans. The Test Success Criteria for the Milestone Achievement Certificates have been agreed by the Parties prior to the Commencement Date and are set out in Annex 4 to this Schedule. For each phase of the Implementation Period, the Test Success Criteria for: each Test that must be Achieved for the Service Provider must Supplier to Achieve for either the ATP Milestone or a Contract Performance Point (“CPP”) Milestone, CPP Milestone are set out in Annex 4annex 4 of this Schedule; and all other Tests shall be agreed between the Parties as part of the relevant Test Plan pursuant to paragraph 5. Following approval of a Test Plan, the Service Provider Supplier shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) 10 Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan). Each Test Specification shall include as a minimum: a mechanism for tracking traceability of Tests being conducted to requirements; the specification of the Test data, including its source, scope, volume and management, a request (if applicable) for relevant Test data to be provided by the Purchaser Authority and the extent to which it is equivalent to live operational data; a plan to make the resources available for Testing; Test scripts; Test pre-requisites pre‑requisites and the mechanism for measuring them; and expected Test results, including: a mechanism to be used to capture and record Test results; and a method to process the Test results to establish their content.

TEST PLANS. 4.1 The Service Provider Contactor shall develop and maintain the Test Plans and submit these for the approval each Test Stage as required by paragraph 1.5 of the Purchaser 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 this Part B. The Contractor shall ensure all Test Plans that are Contractor's Test Documents comply with the Test Strategy or otherwise agree in writing) prior to the start date for the and relevant Testing (as specified in the Implementation Plan)Test Approach. The Purchaser Contractor shall define any additional Tests to be included in the Test Plan for the approval of the Service Provider, ensure each such approval not to be unreasonably withheld or delayed. Each Test Plan shall include include, as a minimum: , the relevant details set out below in relation to the applicable Test definition and the purpose Stage: (a) details of the TestTesting, the Milestone confirmation of any applicable Milestones to which it relatesthe Testing may relate, the requirements being tested Tested and, for each Test, the specific Test Success Criteria (agreed by both Parties) to be satisfied; met; (b) a detailed procedure for the Tests to be carried out, including: : (i) the timetable for the Tests, Tests including start and end dates; dates (in accordance with this Agreement and any applicable Implementation Plan); (ii) a full list of the Testing mechanism, including relevant tools and techniques being used; Test Specifications applicable to each Test Stage; (iii) dates and methods by which the Purchaser DCC can execute its own Tests (where relevant), inspect Test results or witness the Tests in order to establish that the applicable Stage Exit Criteria and Test Success Criteria have been met; ; (iv) dates agreed with the DCC to allow them to conduct identified acceptance activities; (v) the mechanism for ensuring the quality, completeness and relevance of the Tests; ; (vi) the format and an example of Test progress reports and the process with which the Purchaser DCC accesses daily Test schedules; ; (vii) the process with which the Purchaser DCC will use to review Test Issues Incidents and the Service Provider’s progress in resolving these in on a timely basis; ; (viii) the Test schedule; and the re-Test procedure, the timetable and the resources which would be required for re-Testing; the process for escalating Test Issues from a re-test situation to the taking schedule of specific remedial action to resolve the Test Issue. The Purchaser shall not unreasonably withhold or delay its approval of the Test Plans provided that the Service Provider shall incorporate any reasonable requirements of the Purchaser in the Test Plans. The Test Success Criteria for the Milestone Achievement Certificates have been agreed by the Parties prior to the Commencement Date and are set out in Annex 4 to this Schedule. For each phase of the Implementation Period, the Test Success Criteria for: each Test that the Service Provider must Achieve for the ATP Milestone or a Contract Performance Point Tests; (“CPP”ix) Milestone, are set out in Annex 4; and all other Tests shall be agreed between the Parties as part of the relevant Test Plan pursuant to paragraph 5. Following approval of a Test Plan, the Service Provider shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan. Each Test Specification shall include as a minimum: a mechanism for tracking traceability of Tests being conducted to requirements; the specification of the Test dataData, including its source, scope, volume and management, a request (if applicable) for relevant Test data Data to be provided by another person (which may include the Purchaser DCC acting on behalf of the DCC Service Users) with agreed dates at which it shall be provided and the extent to which it is equivalent to live operational data; ; (x) the information required by paragraph 5.1(c) (under the heading Test Data) of Part C (Testing); (xi) a plan to make the resources available for Testing; Testing including any environments, Test scripts; Labs, facilities, model offices, infrastructure, Test prepersonnel, third party and/or DCC involvement; (xii) the re-requisites Test procedure, the timetable and the mechanism resources which would be required for measuring themre-Testing; (xiii) a Traceability Matrix to map Test Specifications to DCC Requirements; and (xiv) the decision making process for escalation from a re-test situation to specific remedial action to resolve the problem / Test Incident. 4.2 The Contractor shall review and expected at all times keep up-to-date (in accordance with the process described in paragraph 6 of this Part B of this Schedule 6.2) each Test resultsPlan it was required to develop and maintain in accordance with this Agreement so as to ensure that they are kept fully up-to-date and accurately reflect the then current status of the relevant Testing Activities (including any arrangements in connection with Future Testing Activities) and otherwise continue to comply with the requirements of this Schedule 6.2. 4.3 The Contractor recognises that Test Plans developed by the Prime DSP are anticipated to include, including: as a mechanism minimum, details equivalent to be used those referred to capture and record Test results; and a method to process the Test results to establish their contentin paragraph 4.1 of this Part.