TEST PLANS. The Supplier shall develop Test Plans for the approval of the Customer as soon as practicable but in any case no later than sixty (60) 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; a detailed procedure for the Tests to be carried out, including: the timetable for the Tests including start and end dates; the Testing mechanism; dates and methods by which the Customer can inspect Test results; the mechanism for ensuring the quality, completeness and relevance of the Tests; the process with which the Customer will review Test Issues and progress on a timely basis; and the re-Test procedure, the timetable and the resources which would be required for re-Testing. The Customer shall not unreasonably withhold or delay its approval of the Test Plans and the Supplier shall implement any reasonable requirements of the Customer in the Test Plans.
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. TEST SUCCESS CRITERIA 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 PLANS. 5.1 The 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 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).
TEST PLANS. The SI shall prepare Test Plans for all Tests set out in the Technical Specifications, including Technical Specifications Section 27 (Factory Testing and Inspection) and Technical Specifications Section 30 (Post- Installation Testing and System Acceptance). The Test Plans shall, at a minimum, detail: (i) the number and range of tests; (ii) the number and type of Failures allowed for acceptance for each phase of testing; (iii) performance measurement procedures; (iv) acceptance criteria; and (v) related requirements and conditions. The SI shall submit all Test Plans to the MTA for its review and approval on the schedule set by the Technical Specifications.
TEST PLANS. Contractor shall produce all necessary component, subsystem, and instrument level test plans. Each plan shall include a detailed test description explaining the “what, how, and why” of each test including test set-up, test objectives, requirements planned to be verified, and a listing of test cases to be executed. The test description will also highlight [**Redacted**]. Test plans shall be available for DigitalGlobe review. Test Plans shall be provided no later than [**Redacted**] before the applicable Test Readiness Review (TRR).
TEST PLANS. Test Plans define actions needed to test a new feature or system, as described more fully below. -------------------------------------------------------------------------------- Schedule A to the Confidential - Winstar/Lucent Supply Agreement - A-13 - Execution Version
TEST PLANS. Lucent will develop test plans and scripts for a structured, hierarchical test program that will verify the functionality of individual Network Elements and the ability of the Network Elements to inter-operate with each other in the Network as described in the WinStar-approved design specifications. The test plans will include test conditions and the anticipated acceptable outcome thresholds (e.g. with regard to interoperability, manageability, engineering guidelines, product specs, Y2K, IEEE, and NEBs compliance).
TEST PLANS. Symetra will be responsible for developing and executing its acceptance test plans in accordance with the transition methodology defined by ACS and approved by Symetra. The following defines the two types of test plans that are applicable. The Application Unit Test is conducted over a window of approximately two to three weeks. This type of testing can be done mid-week via TCP/IP access to the cloned system(s) at ACS. The test plan should contain scripts that Symetra personnel can execute in order to ensure proper function of system and application components as well as interfaces to other test systems. The Acceptance Test Plan is executed four times: at the two Integrated Applications / Network Tests, at the Dry Run, and at the Hot Cut. This plan is comprised of a subset of the functional test scripts. These scripts define “quick hit” tests that can be performed in a short period to verify that the systems have been successfully built and the network has been successfully pointed to ACS. At the Hot Cut, the Acceptance Test Plan execution is the final check to ensure that the environment is healthy prior to a “Go / No-Go” decision. It is essential that this test plan be executed more than once to insure that test scripts are functioning as expected prior to beginning production processing at the ACS data center. Confidential Information Table of Contents Symetra Transition Program
TEST PLANS. For any system that has not attained MR, the contractor shall prepare and submit a Test Plan, DI-NDTI-80566A, for each system(s) prior to PQT, FAT, and for any configuration change after FAT. The test plan shall provide the approach for ensuring the system and/or major components meet the required performance specifications and applicable drawing requirements. The test plan shall include for each specification requirement, as a minimum, the method of validation (e.g., test, demonstration, inspection, analysis, similarity); test conditions and applicable test standards, sample size, test schedules, and test sequences. The test plan shall address all inspections, demonstrations, testing, and analysis required to validate the Product Baseline, including validation of the processes necessary to build the design. For configuration changes after FAT, the test plan shall include a description of all changes, to include the reason for the change(s), performance parameters that could be affected by each implemented change, and all other requirements of this paragraph. Acceptance Testing (AT) required for final Government acceptance shall be identified in the test plan. Any modifications to the test plan shall be agreed to in writing by the Contracting Officer’s Representative (COR) prior to being implemented. FWS-I Test Plans are a deliverable under CDRL-D003.
TEST PLANS. 6.1 Each Test Plan shall include:
