Common use of TESTING OVERVIEW Clause in Contracts

TESTING OVERVIEW. All Tests conducted by the Service Provider shall be conducted in accordance with the Test Strategy, the Test Plans and the Test Specifications. The Service Provider shall not submit any Deliverable for Testing: unless the Service Provider is confident that it will satisfy the relevant Test Success Criteria; until the Purchaser has issued a Test Certificate in respect of any prior, dependant Deliverable(s); and until the Parties have agreed the Test Plan and the Test Specification relating to the relevant Deliverable(s). The Service Provider shall use reasonable endeavours to submit each Deliverable for Testing or re-Testing by or before the date set out in the Implementation Plan, or for any post implementation deployments, for the commencement of Testing in respect of the relevant Deliverable. Prior to the start of testing, both during the Implementation Period and during the Term, the Service Provider must provide the Purchaser with demonstrations/walkthroughs of the main functionality contained in each Deliverable. Prior to the issue of a Test Certificate, the Purchaser shall be entitled to review the relevant Test Reports and the Test Issue Management Log. The provisions of clause 22 (Deliverables and Milestones), clause 24 (Implementation) including 24.3 and 24.4 (Rectification Plan) and 24.5 (Testing and Achievement of Milestones) and clause 26 (Purchaser Cause), shall apply to Testing. Any disputes between the Purchaser and the Service Provider regarding Testing shall be referred to clause 61 (Dispute Resolution). The Purchaser shall issue Test Certificates and grant Milestone Achievement Certificates without unreasonable delay. TEST STRATEGY The Service Provider shall develop the final Test Strategy as soon as practicable after the Commencement 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 Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in accordance with the Implementation Plan and in relation to the release of any additional software updates during the Term; the type of testing to be conducted, which will be based on the nature of the deliverable being tested, e.g. Integration, Regression, Performance, Functional and Non-functional testing; possible approaches to ensure full end to end testing; system provider and third party suppliers, where appropriate; test automation software, tools and procedures; the procedure for the Purchaser to develop acceptance tests to be signed off by both the Service Provider and the Purchaser, as required; the Purchaser to execute the agreed acceptance tests; the process to be used to capture and record Test results and the categorisation of Test Issues; the method for mapping the expected Test results to the Test Success Criteria; the procedure to be followed if a Deliverable fails to satisfy the Test Success Criteria or produces unexpected results, to include the method used to raise, view and track defects during testing; the 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 and reporting, 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 Purchaser's and the Service Provider's Test representatives; a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and Purchaser and/or third party involvement in the conduct of the Tests; the technical environment required to support the Tests; and the procedure for managing the configuration of the Test environments.