Common use of TEST SPECIFICATIONS Clause in Contracts

TEST SPECIFICATIONS. 5.1 The Contractor shall produce a Test Specification for each Test and shall ensure this complies with the relevant Test Plan for the relevant Test Stage. 5.2 The Contractor shall provide all relevant Test Specifications required for each Test Stage by no later than twenty (20) Working Days before the start date for any Testing for the relevant Test Stage to which such Stage relates (as set out in the Implementation Plan, Test Plan or otherwise agreed pursuant to this Agreement). Each Test Specification shall then be agreed with the DCC in accordance with the process set out in paragraph 6 immediately below. The Contractor shall consider the ability of the DCC to review a large volume of Test Specifications at one time and agree with the DCC a detailed plan to bundle Test Specifications up so as to allow effective review. 5.3 Save as otherwise agreed: (a) the Contractor shall be responsible for creating Test Specifications showing traceability of Tests to the functional and the non-functional requirements as set out in this Agreement and the Contractor Solution Design Documents and Service Management Framework as defined in Schedule 6.3; (b) there shall be Test Specifications for each Test Stage (and each Test); and (c) Tests Specifications shall contain, as a minimum, the following; (i) objective(s) and description of the relevant Test; (ii) Test reference ID; (iii) the date the Test Specification was created; (iv) traceability of the Test Specification to specific Requirements via the Traceability Matrix; (v) the Smart Metering Devices and other equipment and / or Test Stubs to be used in the Test; (vi) execution status including a record of all dates the Test Specification was run; (vii) details of the testing conditions including pre-requisites; (viii) Test execution steps, including negative tests of exception and error conditions; (ix) expected Test results; (x) the Test Success Criteria; and (xi) tester name or identifier.

TEST SPECIFICATIONS. 5.1 The Contractor shall produce a Test Specification for each Test and shall ensure this complies with the relevant Test Plan for the relevant Test Stage. 5.2 The Contractor shall provide all relevant Test Specifications required for each Test Stage by no later than twenty (20) Working Days before the start date for any Testing for the relevant Test Stage to which such Stage relates (as set out in the Implementation Plan, Test Plan or otherwise agreed pursuant to this Agreement). Each Test Specification shall then be agreed with the DCC in accordance with the process set out in paragraph 6 immediately below. The Contractor shall consider the ability of the DCC to review a large volume of Test Specifications at one time and agree with the DCC a detailed plan to bundle Test Specifications up so as to allow effective review. 5.3 Save as otherwise agreed: (a) the Contractor shall be responsible for creating Test Specifications showing traceability of Tests to the functional and the non-functional requirements as set out in this Agreement and the Contractor Solution Design Documents and Service Management Framework and Communications Hub Documents as defined in Schedule 6.3; (b) there shall be Test Specifications for each Test Stage (and each Test); and (c) Tests Specifications shall contain, as a minimum, the following; (i) objective(s) and description of the relevant Test; (ii) Test reference ID; (iii) the date the Test Specification was created; (iv) traceability of the Test Specification to specific Requirements via the Traceability Matrix; (v) the Smart Metering Devices and other equipment and / or Test Stubs to be used in the Test; (vi) execution status including a record of all dates the Test Specification was run; (vii) details of the testing conditions including pre-requisites; (viii) Test execution steps, including negative tests of exception and error conditions; (ix) expected Test results; (x) the Test Success Criteria; and (xi) tester name or identifier.