TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable after the Call Off Commencement Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree) after the Call Off Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in accordance with 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 if a Deliverable fails to satisfy the Test Success Criteria or 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 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.
TEST STRATEGY. 2.1 The Prime DSP shall develop and maintain the Test Strategy that shall describe, at a high-level, the 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 connection with their respective DCC Service Provider Contract (including in connection with Enduring Testing).
2.2 Not used.
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 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;
(c) the Testing procedure including details, amongst other things, of the scope of each Test Phase in accordance with the Test Requirements;
(d) the process to be used to capture and record Test results and the categorisation of Test Incidents;
(e) the method for mapping the expected Test results to the Test Success Criteria;
(f) the procedure to be followed should the Test Success Criteria not be met or Test results fail to be as expected or any Stage Exit Criteria not be met, including any rectification procedure;
(g) the process for the production and maintenance of Test Reports and reporting, including (if applicable) templates for the Test Reports and the Contractor’s Test Incident Management Log (or where appropriate the Prime DSP's Test Incident Management Log), and a sample plan to resolve Test Incidents;
(h) the names and contact details of the DCC’s representatives (if applicable), relevant Other Service Providers' representatives and the 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 DCC and/or third party 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
(n) the sourcing of Test Data (including confirmation of agreement...
TEST STRATEGY. 4.1 The Supplier shall develop the final Test Strategy as soon as practicable after the Effective Date but in any case no later than 20 Working Days (or such other period as the Parties may agree in writing) after the Effective Date.
4.2 The final Test Strategy shall include:
(a) an overview of how Testing will be conducted in accordance with the Implementation Plan;
(b) the process to be used to capture and record Test results and the categorisation of Test Issues;
(c) the method for mapping the expected Test results to the Test Success Criteria;
(d) the procedure to be followed if a Deliverable fails to satisfy the Test Success Criteria or produces unexpected results, including a procedure for the resolution of Test Issues;
(e) the procedure to be followed to sign off each Test;
(f) the process for the production and maintenance of Test Reports and reporting, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues;
(g) the names and contact details of the Authority's and the Supplier's Test representatives;
(h) a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and Authority and/or third party involvement in the conduct of the Tests;
(i) the technical environments required to support the Tests; and
(j) the procedure for managing the configuration of the Test environments.
TEST STRATEGY. 2.3.1 Unless otherwise agreed, EHI shall develop with the Customer a test strategy as part of the Implementation Plan, which shall include:
2.3.1.1 an overview of how testing will be conducted in relation to the Implementation Plan;
2.3.1.2 the process to be used to capture and record test results and the categorisation of test issues;
2.3.1.3 the method for mapping the expected test results to the Acceptance Criteria;
2.3.1.4 the procedure to be followed should a deliverable fail to satisfy the test criteria or produce unexpected results including a procedure for the resolution of test issues;
2.3.1.5 the procedure to be followed to sign off each Milestone;
2.3.1.6 a high-level identification of the resources required for testing of each partty, including facilities, infrastructure, personnel and Customer and/or third party involvement in the conduct of the Tests.
TEST STRATEGY. The Contact Center contingency plans strategy consists of halting one of the attendance hubs once a week (always on Sundays), it will remain shut down, the attendants are release and the calls are redirected to one of the other hubs. The hub shutdown schedule and the evidence of its performance (statistics for the day with the number of calls answered at each hub) will be the RESPONSIBILITY OF THE PARTNER (PLANNING/OPERATIONS)
TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable but in any case no later than sixty (60) Working Days (or such other period as the Parties may agree) after the Call Off Commencement Date.
TEST STRATEGY. 11.1 The Contractor shall develop the final Test Strategy as soon as practicable but in any case no later than [ ] Working Days (or such other period as the parties may agree) after the Effective Date.
11.2 The final Test Strategy shall include:
11.2.1 an overview of how Testing will be conducted in relation to the Implementation Plan;
11.2.2 the process to be used to capture and record Test results and the categorisation of Test Issues;
11.2.3 the method for mapping the expected Test results to the Test Success Criteria;
11.2.4 the procedure to be followed should a Deliverable fail to satisfy the Test Success Criteria or to produce unexpected results, including a procedure for the resolution of Test Issues;
11.2.5 the procedure to be followed to sign off each Test;
11.2.6 the process for the production and maintenance of Test Reports and reporting, including templates for the Test Reports and the Test Issue Management Log, and a sample plan to resolve Test Issues;
11.2.7 the names and contact details of the Authority's and the Contractor's Test representatives;
11.2.8 a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and Authority and/or third party involvement in the conduct of the Tests;
11.2.9 the technical environments required to support the Tests; and
11.2.10 the procedure for managing the configuration of the Test environments.
TEST STRATEGY. 2.3.1 Unless otherwise agreed, MAGENTUS shall develop with the Customer a test strategy as part of the Implementation Plan, which shall include:
2.3.1.1 an overview of how testing will be conducted in relation to the Implementation Plan;
2.3.1.2 the process to be used to capture and record test results and the categorisation of test issues;
2.3.1.3 the method for mapping the expected test results to the Acceptance Criteria;
2.3.1.4 the procedure to be followed should a deliverable fail to satisfy the test criteria or produce unexpected results including a procedure for the resolution of test issues;
2.3.1.5 the procedure to be followed to sign off each Milestone;
2.3.1.6 a high-level identification of the resources required for testing of each partty, including facilities, infrastructure, personnel and Customer and/or third party involvement in the conduct of the Tests.
TEST STRATEGY. 4.1 The Supplier will develop and maintain a Test Strategy as soon as practicable after the Effective Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in writing) after the Effective Date.
4.2 The final Test Strategy shall apply to all Deliverables implemented under this Agreement, and shall, save as agreed in writing otherwise by the Parties, include:
4.2.1 an overview of how Testing will be conducted in accordance with the Implementation Plan and demonstrating how different Test Phases may be used for Deliverables;
4.2.2 the process and methods to be used to capture and record Test results and the categorisation of Defects;
4.2.3 Test suspension and resumption criteria;
4.2.4 the method for mapping the expected Test results to the Test Success Criteria;
4.2.5 the procedure to be followed if a Deliverable fails to satisfy the Test Success Criteria or produces unexpected results, including a procedure for the resolution of Defects including Functional, Non-Functional and Regression Testing elements;
4.2.6 the procedure to be followed to sign off each Test;
4.2.7 the process for the production and maintenance of Test Reports and reporting, including templates for the Test Reports and the Defect Log;
4.2.8 the names and contact details of Network Rail's and the Supplier's Test representatives;
4.2.9 a high level identification of the resources required for Testing, including facilities, infrastructure, tools, personnel and Network Rail and/or third party involvement in the conduct of the Tests;
4.2.10 the technical environments required to support the Tests;
4.2.11 the procedure for managing the configuration of the Test environments;
4.2.12 the risks, assumptions, issues and dependencies associated with the Test Strategy; and
4.2.13 details of Entry and Exit Criteria for each Test Phase.
TEST STRATEGY. 7.3.1 The version of the Test Strategy agreed at the Effective Date, and containing full details of the testing (where applicable) of each Milestone type and full details for how each Milestone testing procedure will apply to each applicable Phase of the Supplier Solution, is set out in Appendix 4.
7.3.2 The Test Strategy shall include:
(a) an overview of how Testing shall be conducted in relation to the Implementation Plan and the Project Plan;
(b) the Test Success Criteria for each applicable Test;
(c) the process to be used to capture and record Test results and Test issues and a procedure for the resolution of Test issues;
(d) the method for mapping the expected Test results to the Test Success Criteria;
(e) the names and contact details of the Authority's and the Supplier's Test representatives; and
(f) a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and/or the third party involvement in the conduct of the Tests.
7.3.3 No later than 20 Working Days prior to the planned start date for a Phase, the Supplier shall provide to the Authority for approval an updated Test Strategy (to the extent such updates are required taking into account the existing content of the Test Strategy) providing full details for that Phase in accordance with paragraph 7.3.2.
7.3.4 As soon as reasonably practicable and in any event within five (5) Working Days of receipt the Authority shall notify the Supplier that it either approves the updates to the draft Test Strategy (in which case it shall become the Test Strategy for the purpose of this Contract) or, acting reasonably, requires the draft Test Strategy to be amended and/or developed further (in which case the Supplier shall provide such revised drafts as is necessary, taking into account any reasonable comments provided by the Authority, until the Test Strategy is approved by the Authority). The Authority's approval of any Test Strategy shall not be unreasonably withheld or delayed.
