Integration Testing. Integration Testing is performed by developers after integrating completed components or modules into the overall system codebase. This testing is done in order to ensure that the completed components or modules work at a high level and that existing components and shared components have not been broken by the new module. The selected Vendor shall include its approach to Integration Testing, including the recommended environment for Integration Testing, in its Test Plan. Integration testing guidelines shall be included in development standards documentation.
Integration Testing. Integration testing is intended to verify operational requirements between major applications, sub-systems, or modules. Test cases should be constructed to test that all modules interact correctly. Likewise, an Integration Test should be defined for each of the “Integration and Interfaces” requirements identified in the application specifications spreadsheet.
Integration Testing. This is an important part of the solution validation, where the interaction between the different external systems and Open Smartflex is tested. Since Integration Testing involves several external systems and platforms, the participation of subject matter experts in these systems and platforms is mandatory. This testing process is executed by the project team (City and Open) during the Client Solution Set-up.
Integration Testing. Notwithstanding the Authority’s acceptance of any Deliverable, upon delivery of the final completed Website, the Authority shall have the right to perform additional tests on each previously-accepted Development Deliverable to ensure full integration and compatibility with all elements of the Website. The Authority shall perform such testing, and the Consultant shall correct any nonconformities, in accordance with the procedures set forth in Section 4.3, as though each such Development Deliverable were delivered on the date of delivery of the final Website.
Integration Testing. Integration testing is essential to ensure that the application to be deployed does not disrupt the DC operations and affect other DC infrastructure in terms of performance and security. The technical tasks to be carried out shall be as follows:
Integration Testing. 1. The Contractor shall perform integration hardware and software testing throughout the development process as required by Contractor ISO 9001 (or equivalent) process.
Integration Testing. 1. After set-up, the OPUS Implementation Team will inform SiVault of its readiness to conduct integration testing.
Integration Testing. 1. The Contractor shall perform integration testing as part of the development process.
Integration Testing. For a period of [*] from the date of shipment by Seagate, LSI may conduct integration testing to confirm that the Product conforms to any mutually agreed upon specifications. Product found to be nonconforming ("DOA") within the initial [*] period may be returned by LSI to Seagate for credit to LSI's account in an amount equal to the purchase price paid. Product returned by LSI must be in Seagate standard packaging unless otherwise agreed to by the parties. LSI will provide Seagate with a purchase order for any replacement Product it elects to order. Seagate will pay for the return of the Product to Seagate, provided a Seagate designated carrier is utilized. Transportation charges associated with replacement Product shipped to LSI will be borne by Seagate.
Integration Testing. As part of the Agreed Project Plan, Sprint and Purchaser will jointly develop an integration test plan that details the integration tests that will be executed to verify that the Network Elements are integrated with the Sprint Network and function in accordance with the requirements and designs agreed upon by the Parties, including the specifications set forth in this Integration SOW and the Agreed Project Plan. The Parties will perform the following integration test activities: • Sprint will perform integration testing to ensure the Sprint Network is performing in accordance with the requirements and designs agreed upon by the Parties in the Agreed Project Plan. • Sprint will perform integration testing to ensure the Sprint interfaces to the Purchaser’s Network Elements are functioning correctly and adhere to the interface specifications defined and agreed upon between the Parties in the Agreed Project Plan. • Purchaser will perform integration testing to ensure the Purchaser’s Network Elements are performing in accordance with the requirements and designs agreed upon by the Parties in the Agreed Project Plan. • Purchaser will perform integration testing to ensure the interfaces from the Purchaser’s Network Elements are functioning correctly and adhere to the interface specifications defined and agreed upon between the Parties in the Agreed Project Plan. • Sprint will provide assistance to Purchaser to help troubleshoot issues within the Purchaser’s Network Elements related to the interface between Sprint Network and the Purchaser’s Network Element. The Parties shall conduct Integration testing in accordance with the integration test plan. Integration testing will be conducted during intervals that shall be defined in the Agreed Project Plan.
