Regression Testing. 1. The Hosting Entity must provide when possible regression testing. The regression testing should be applied when significant changes have been applied to the EuroHPC supercomputer to verify that previous applications still work with the new changes.
Regression Testing. Do the unmodified functions still operate as expected after a change has been introduced? Does everything work together as before after all changes and fixes have been introduced?
Regression Testing. A regression test procedure shall be exercised by the Contractor for each new software release. * Portions of this document marked with **** have been omitted pursuant to a request for confidential treatment submitted with the SEC. The original contracts have been filed separately with the SEC as part of the confidential treatment request. Ref: INMARSAT GLOBALISED VOICE Issue: Draft V2.8h Date: Page: 56 of 81 Inmarsat Globalised Voice Project 06-4318 Statement of Work
Regression Testing. 1. A regression test procedure shall be exercised by the Contractor for each new software release.
Regression Testing. 10.1 The Contractor shall ensure that Regression Testing forms an integral part of all Test Plans (and all Test Stages for which it is responsible for developing Test Plans).
10.2 The Contractor shall establish a Regression Test method, Regression Test Packs (including Test Data and Test results) and implement a detailed approach for ensuring continued delivery of quality systems.
10.3 The Contractor shall carry out Regression Testing for all Deliverables, the Contractor Solution or (in either case) any relevant part where functionality is delivered in stages and as agreed under the Change Control Procedure.
10.4 A full Regression Test Pack shall be run by the Contractor each and every time a change is applied to the Contractor Solution and before delivery to the DCC or into live operation. The DCC shall agree with the Contractor which changes (including security patches and emergency changes) may be subject to a fast- track process.
10.5 The Contractor shall produce and deliver to the DCC (and the Lead Contractor where the Contractor is not the Lead Contractor) by the end of each Test Stage a Regression Test Pack for the Contractor Solution and keep it updated throughout all subsequent Testing (such Regression Test Packs will be utilised, amongst others, by the Prime DSP and DCC on an on-going basis). Where reasonably practical the Contractor shall provide that these Regression Test Packs shall be automated.
10.6 The Contractor shall promptly (and in any event within two (2) Working Days) rectify any omissions in any Regression Test Pack in the event that the receiving party (i.e. the DCC or Prime DSP) identifies any faults or omissions.
Regression Testing. 10.1 The Contractor shall ensure that Regression Testing forms an integral part of all Test Plans (and all Test Stages for which it is responsible for developing Test Plans).
10.2 The Contractor shall establish a Regression Test method, Regression Test Packs (including Test Data and Test results) and implement a detailed approach for ensuring continued delivery of quality systems.
10.3 The Contractor shall carry out Regression Testing for all Deliverables, the Contractor Solution or (in either case) any relevant part where functionality is delivered in stages and as agreed under the Change Control Procedure.
10.4 A full Regression Test Pack shall be run by the Contractor each and every time a change is applied to the Contractor Solution and before delivery to the DCC or into live operation. The DCC shall agree with the Contractor which changes (including security patches and emergency changes) may be subject to a fast- track process.
10.5 The Contractor shall produce and deliver to the DCC by the end of each Test Stage a Regression Test Pack for the Contractor Solution and keep it updated throughout all subsequent Testing (such Regression Test Packs will be utilised, amongst others, by the DCC on an on-going basis). Where reasonably practical the Contractor shall provide that these Regression Test Packs shall be automated.
10.6 The Contractor shall promptly (and in any event within two (2) Working Days) rectify any omissions in any Regression Test Pack in the event that the receiving party (i.e. the DCC) identifies any faults or omissions.
Regression Testing. Regression Testing consists of Functionality Testing (defined in Paragraph 14(a)(i)) and shall test (A) the Functionality of Release 1.2 together with Release 1.1; (B) the Functionality of Release 1.
Regression Testing. This is a standard phase of testing run as the final release date nears. As builds come out, we will do "spot testing" on changed areas, but we will also do full regression testing of all test cases against a build to insure that areas previously working are still operating to expectations. Branding Kit for Synchrologic Suite PPC Devices Product Branding Worksheet PocketPC Client Synchrologic Email Accelerator – SEA Synchrologic Systems Management – SSM Synchrologic File Sync — SFS Branding Kit for Synchrologic Suite PPC Devices
Regression Testing. Regression testing should be completed after integration of each major component into the wider system to ensure that components which have already been tested are still working. Regression testing should also be completed after every migration of new build versions to each test environment. Regression test scenarios shall be a subset of System Test scenarios, agreed upon with CHFS, chosen to ensure maximum functional and technical coverage of regression testing. The selected Vendor shall include its approach to Regression Testing in its Test Plan. The approach should include the use of an automated test tool to minimize the cycle time and resources required to complete regression testing.
Regression Testing. 4.1 In some projects service delivery will commence on a phased basis i.e. not all services will have the same commencement date and/or additional elements of a given service stream will be introduced at different stages. Typically this would arise in relation to a migration from a legacy system(s) where the former service is wound down as the new service comes on-stream, or where increased capacity or functionality is required incrementally over a period of time. Generally, each phase of the implementation will have a Milestone and set of Deliverables which will be subject to Testing. It is important that the Authority does not affirm through Testing that phase Deliverables are ready for Service, which are proven to work in isolation but which have not been proven to work in combination with Deliverables from another phase (as part of the Contractor System). The Deliverables for each phase should be tested in conjunction with the previous phases. At the final phase, the Contractor System must be tested in its entirety and the successful testing of all Deliverables together should be a pre- requisite of the final Milestone and Authority to Proceed to full Service provision. This form of testing is commonly known as "regression testing".
4.2 In the case of a phased implementation, clause 4 of the Agreement (Testing) should make it clear that testing of each phase/Milestone is an interim test. Final testing of Service readiness is not achieved until all related Deliverables have been comprehensively tested together as a whole. In the event that the Deliverables do not meet the Test Success Criteria and Authority to Proceed cannot be given by the Authority, it should reserve the right to reject all or some of the phases/Milestones regardless of their earlier interim testing. The Authority should also reserve the right to clawback any payments made to the Contractor in respect of Milestone Achievement (see paragraph 2.4 of Part A of Schedule 7.1 (Charges and Invoicing)). These provisions are fundamental for creating the appropriate risk profile for an Authority in an ICT service agreement, as they ensure that performance risk is not transferred back from the Contractor to the Authority. It is of paramount importance that these provisions are included and their effectiveness is not diluted by negotiation.
4.3 A phased testing has key advantages in ensuring successful project delivery for the following reasons:
4.3.1 the Deliverables can be linked to Delay Payme...
