Testing Support Clause Samples

Testing Support. The Contractor shall provide all testing necessary to accomplish the Government's requirements. The Contractor shall provide testing support, using one or more of a variety of approaches, specific to the Government's needs and delivery order requirements. Testing support may include, but is not limited to, hardware, software, system, and network testing, and may include, at a minimum, such tasks as: test plan development installation and operational testing of equipment system and software development testing system and software qualification testing system and software acceptance testing independent system and software validation testing network testing, both before and after integration activities
View Source
Testing Support. Purpose To outline the contractor’s responsibilities during system testing. Content The contractor will monitor testing results, conference at least twice weekly during testing with State to discuss identified problems, and promptly develop a resolution to the identified problems. Acceptance State will review progress made with identified problems during testing and when all are resolved to the State’s satisfaction, this deliverable will be considered completed.
View Source
Testing Support. Provide engineering testing at the Auburn Hills and Caro Test Centers consistent with past custom and practice, at no charge, for a period of one year from the Closing Date, with respect to the Business subject to customary disclaimers for the automotive testing industry.
View Source
Testing Support. Starboard will support Unit Testing, End-to-End Testing with the TAA IT team, and User Acceptance Testing (UAT) by the TAA Maintenance and IT teams. Starboard will monitor the testing log and work to resolve any reported defects. UAT will be performed in the Test Maximo environment and verify the integration is working as designed. Testing will include both the inbound meter data and the follow up work generation.
View Source
Testing Support 
View Source

Related to Testing Support

  • Marketing Support Planet Payment will provide such marketing support as Acquirer may reasonably require in connection with marketing the Acquirer Program to Merchants, including but not limited to: (a) The participation of Planet Payment personnel at meetings (if available) or conference calls with Merchants; (b) Assistance in the creation of collateral materials; (c) Assistance in the drafting of contractual agreements and addenda for Acquirers; (d) Assistance in training Merchants in the use of Planet Payment’s systems and reports, which will be made available to them under the Acquirer Program and the operation of the Acquirer Program, including but not limited to use of Planet Payment’s MWEB on-line reporting system and providing suitable training materials.

  • Engineering Support When requested by CLEC, CBT shall provide timely engineering support. CLEC shall pay CBT for the use of its engineering services at charges previously agreed to by CLEC.

  • TESTING SERVICES DESCRIPTION This Exhibit contains additional terms and conditions applicable to testing services for digestive disorders (the “Testing Services”) that you may have purchased. The additional terms and conditions in this Exhibit only apply to the services described in this Exhibit.

  • Performance Testing (a) All performance tests of the Project, including any Initial Performance Test required in Section 2 of Appendix VIII, will be performed in accordance with the test procedures set forth in Appendix VIII (“Performance Test”), including additional procedures and protocols related to Performance Testing as mutually agreed between Buyer and Seller (“Test Procedures”). Seller shall bear all costs and receive all revenues, if applicable, associated with all Performance Tests. (b) After the Initial Delivery Date and during the Delivery Term, Buyer will have the right to conduct a Performance Test (“Buyer Performance Test”) no more than once a calendar year to demonstrate whether the Project is capable of delivering the Distribution Services at the Contract Capacity. Within 30 calendar days following a Buyer Performance Test, Seller will have the right to retest the Project with a Performance Test (“Seller Retest”). For the avoidance of doubt, the results of any Seller Retest will supersede the results of the preceding Buyer Performance Test. (i) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at or above ninety-nine percent (99%) of the Initial Contract Capacity, the Contract Capacity will remain the Initial Contract Capacity; (ii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is capable of delivering Distribution Services at more than or equal to eighty-five (85%) of the Initial Contract Capacity, but less than ninety-nine percent (99%) of the Initial Contract Capacity (“Testing Band”), the Contract Capacity will be automatically adjusted (upwards or downwards) to the capacity commensurate with the amount of Distribution Services the Project delivered during the Performance Test within the Testing Band. (iii) If a Buyer Performance Test or, if a corresponding Seller Retest has occurred, a Seller Retest demonstrates the Project is not capable of delivering Distribution Services of at least eighty-five percent (85%) of the Initial Contract Capacity, an Event of Default shall occur in accordance with Section 7.1(a)(viii).

  • ODUF Testing 6.6.1 Upon request from TWTC, AT&T shall send ODUF test files to TWTC. The Parties agree to review and discuss the ODUF file content and/or format. For testing of usage results, AT&T shall request that TWTC set up a production (live) file. The live test may consist of TWTC’s employees making test calls for the types of services TWTC requests on ODUF. These test calls are logged by TWTC, and the logs are provided to AT&T. These logs will be used to verify the files. Testing will be completed within thirty (30) days from the date on which the initial test file was sent.