TEST PLANS. 12.1 The Contractor shall develop Test Plans for the approval of the Authority as soon as practicable but in any case no later than [ ] 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. 12.2 Each Test Plan shall include as a minimum: 12.2.1 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 met; 12.2.2 a detailed procedure for the Tests to be carried out, including: 12.2.2.1 the timetable for the Tests including start and end dates; 12.2.2.2 the Testing mechanism; 12.2.2.3 dates and methods by which the Authority can inspect Test results or witness the Tests in order to establish that the Test Success Criteria have been met; 12.2.2.4 the mechanism for ensuring the quality, completeness and relevance of the Tests; 12.2.2.5 the format and an example of Test progress reports and the process with which the Authority accesses daily Test schedules; 12.2.2.6 the process with which the Authority will review Test Issues and progress on a timely basis; 12.2.2.7 the Test schedule; 12.2.2.8 the re-Test procedure, the timetable and the resources which would be required for re-Testing; and 12.2.2.9 the decision making process for escalation from a re-test situation to specific remedial action to resolve the problem / Test Issue. 12.3 The Authority shall not unreasonably withhold or delay its approval of the Test Plans and the Contractor shall implement any reasonable requirements of the Authority in the Test Plans.
Appears in 1 contract
Sources: Ict Services Agreement
TEST PLANS. 12.1 The Contractor 5.1 For each Deliverable, the Supplier shall develop Test Plans and submit these for the approval of the Authority Network Rail as soon as practicable but in any case no later than [ ] twenty (20) Working Days (or such other period as the parties Parties may agree in the Test Strategy or otherwiseotherwise agree in writing) prior to the start date for the relevant Testing (as specified in the Implementation Plan).
12.2 5.2 Each Test Plan shall include as a minimum:
12.2.1 5.2.1 the relevant Test definition and the purpose of the Test, the Milestone to which it relates, the requirements being Tested (these should be presented as a requirements traceability matrix) and, for each Test, the specific Test Success Criteria to be metsatisfied;
12.2.2 5.2.2 a detailed procedure for the Tests to be carried out, including:
12.2.2.1 5.2.2.1 details of which Test phases and environments from the Test Strategy will be employed for each Deliverable;
5.2.2.2 a reference to the components detailed in the Test Strategy that shall be within the scope of Testing for each Deliverable;
5.2.2.3 the timetable for the Tests Tests, including start start/end dates and end datesthose by which documentation will be available for review in order to establish whether Test Success Criteria has been met;
12.2.2.2 5.2.2.4 the Testing mechanism;
12.2.2.3 5.2.2.5 dates and methods by which the Authority Network Rail can inspect Test results or witness the Tests in order to establish that the Test Success Criteria have been met;
12.2.2.4 5.2.2.6 the dates by which documentation will be available for review in order to establish that Test Success Criteria have been met;
5.2.2.7 the mechanism for ensuring the quality, completeness and relevance of the Tests;
12.2.2.5 5.2.2.8 the format and an example of Test progress reports and the process with which the Authority Network Rail accesses daily Test schedulesSchedules;
12.2.2.6 5.2.2.9 the process with which Network Rail will use to review Defects and the Authority will review Test Issues and Supplier’s progress on in resolving these in a timely basis;
12.2.2.7 5.2.2.10 the Test scheduleSchedule;
12.2.2.8 5.2.2.11 the re-Test procedure, the timetable and the resources which would be required for re-Testing; and;
12.2.2.9 5.2.2.12 the decision making process for escalation escalating Defects from a re-test Test situation to the taking of specific remedial action to resolve the problem / Defect;
5.2.2.13 links to Test IssueSpecifications/scripts;
5.2.2.14 details of Entry and Exit criteria specific to each phase of the project;
5.2.2.15 named resources for the roles deemed necessary from the Test Strategy;
5.2.2.16 details of any risks, issues, assumptions or dependencies specific to Testing the Deliverable not already mentioned in the Test Strategy; and
5.2.2.17 details of Test deliverables pertaining to each Deliverable.
12.3 The Authority 5.3 Network Rail shall not unreasonably withhold or delay its approval of the Test Plans and provided that the Contractor Supplier shall implement incorporate any reasonable requirements of the Authority Network Rail in the Test Plans.
Appears in 1 contract
Sources: It Solutions and System Integration Services Agreement
TEST PLANS. 12.1 5.1 The Contractor Supplier shall develop Test Plans and submit these for the approval of the Authority as soon as practicable but in any case no later than [ ] 20 Working Days (or such other period as the parties Parties may agree in the Test Strategy or otherwiseotherwise agree in writing) prior to the start date for the relevant Testing (as specified in the Implementation Plan).
12.2 5.2 Each Test Plan shall include as a minimum:
12.2.1 a) the relevant Test definition and the purpose of the Test, the Key Milestone/ Milestone to which it relates, the requirements being Tested tested and, for each Test, the specific Test Success Criteria to be metsatisfied;
12.2.2 b) a detailed procedure for the Tests to be carried out, including:
12.2.2.1 i) the timetable for the Tests Tests, including start and end dates;
12.2.2.2 ii) the Testing mechanism;
12.2.2.3 iii) dates and methods by which the Authority can inspect Test results or witness the Tests in order to establish that the Test Success Criteria have been met;
12.2.2.4 iv) the mechanism for ensuring the quality, completeness and relevance of the Teststests;
12.2.2.5 v) the format and an example of Test progress reports and the process with which the Authority accesses daily Test schedules;
12.2.2.6 vi) the process with which the Authority will use to review Test Issues and the Supplier’s progress on in resolving these in a timely basis;
12.2.2.7 vii) the Test scheduleSchedule;
12.2.2.8 viii) the re-Test procedure, the timetable and the resources which would be required for re-Testing; and
12.2.2.9 ix) the decision making process for escalation escalating Test Issues from a re-test situation to the taking of specific remedial action to resolve the problem / Test Issue.
12.3 5.3 The Authority shall not unreasonably withhold or delay its approval of the Test Plans and provided that the Contractor Supplier shall implement incorporate any reasonable requirements of the Authority in the Test Plans.
Appears in 1 contract
Sources: Service Agreement