TEST STRATEGY Clause Samples
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. 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 sched...
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. 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 or where a Deliverable produces unexpected results, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; and the process for the production and maintenance of reports relating to Tests.
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 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.
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. 3.1 The Supplier shall develop the final Test Strategy as soon as practicable but in any case no later than 60 Working Days (or such other period as the parties may agree) after the Commencement Date.
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, 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.