Common use of TESTING STRATEGY PLANS Clause in Contracts

TESTING STRATEGY PLANS. The Supplier shall develop Testing Strategy 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 Testing Strategy 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 in a timely basis; 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 Testing Strategy Plans provided that the Supplier shall implement any reasonable requirements of the Customer in the Testing Strategy Plans.

Appears in 5 contracts

Samples: Agreement, Local Authority Software Applications Call Off Terms, Local Authority Software Applications Call Off Terms

AutoNDA by SimpleDocs
Time is Money Join Law Insider Premium to draft better contracts faster.