TEST SPECIFICATIONS Sample Clauses

TEST SPECIFICATIONS. Sunrun and Contractor will perform the following test at the beginning and end of the test period. Capitalized terms contained herein have the meanings set forth in the Master Solar Facility Turnkey Contract.
AutoNDA by SimpleDocs
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. 6.1 The Service Provider shall: (A) in accordance with the applicable Milestone Dates and the Test Strategy, develop a Test Specification for Testing; (B) ensure that each Test Specification is at all times accurate, up to date and complete, including without limitation in respect of the changing functionality of the Services, and as a result of any Changes or Internal Changes; (C) include in each Test Specification at least the following information: (1) the Test Criteria with a reference back to the Service Provider’s Technical Solution and any other documents relevant to the Testing. (2) a set of Test scenarios (including without limitation business process scenarios (where applicable)) and Test Cases designed to exercise all the Test Criteria identified within the Test Specification, each with a reference to the Test Criteria covered by the Test scenario; (3) a set of Test scripts corresponding to the Test scenarios and Test Cases describing the purpose of the Test, the data requirements for the Test, any pre-requisites for the Test, the actions to be taken during the Test, and the expected results for each step or action of the Test against which success or failure of the Test shall be judged; and (D) ensure that all requirements specified in this Agreement in respect of Testing are properly and adequately covered by the Test Criteria.
TEST SPECIFICATIONS. 7.1 The Service Provider shall: (A) in accordance with the applicable Milestones and Milestone Dates and the Test Strategy, develop a Test Specification for each Test Stage; (B) ensure that each Test Specification is at all times accurate, up to date and complete, including in respect of the changing functionality of the: (1) LCHS Assets and Service Systems; (2) Changes; and (3) Internal Changes; (C) ensure that as a minimum each Test Specification includes the following information: (1) the Test Criteria with a reference to the: (a) Statement of Requirements; (b) Design Documents; and (c) any other documents relevant to the Testing as applicable to the Test Stage; (2) a set of: (a) Test scenarios (including business process scenarios (where applicable)); and (b) Test Cases designed to exercise all the Test Criteria identified within the Test Specification, each with a reference to the Test Criteria covered by the Test scenario; and (3) a set of Test scripts which: (a) corresponds with the Test scenarios and Test Cases; (b) describes the: (i) purpose of the Test; (ii) the Test Data requirements; (iii) any pre-requisites for the Test; (iv) actions to be taken during the Test; and (v) the expected results for each step or action of the Test against which success or failure of the Test shall be judged; and (D) ensure that all requirements specified in this Agreement in respect of Testing are properly and adequately covered by the Test Criteria so as to meet the: (1) Statement of Requirements; (2) Design Documents; and (3) any other documents relevant to the Testing.
TEST SPECIFICATIONS. 8.2.1 The release testing specified for this project must be captured in a master specification document that is approved by SAIC-XXXXXXXXX, INC.
TEST SPECIFICATIONS. Every part must be verified according to the characteristics provided by the manufacturer. Every part must be functionally verified according to current state of the art practices.

Related to TEST SPECIFICATIONS

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Product Specifications (a) Supplier shall manufacture all Products according to the Specifications in effect as of the date of this Agreement, with such changes or additions to the Specifications of the Products related thereto as shall be requested by Buyer in accordance with this Section or as otherwise agreed in writing by the Parties. All other Products shall be manufactured with such Specifications as the Parties shall agree in writing. (b) Buyer may request changed or additional Specifications for any Product by delivering written notice thereof to Supplier not less than one hundred twenty (120) days in advance of the first Firm Order for such Product to be supplied with such changed or additional Specifications. Notwithstanding the foregoing, if additional advance time would reasonably be required in order to implement the manufacturing processes for production of a Product with any changed or additional Specifications, and to commence manufacture and delivery thereof, Supplier shall so notify Buyer, and Supplier shall not be required to commence delivery of such Product until the passage of such additional time. (c) Supplier shall be required to accommodate any change of, or additions to, the Specifications for any Product, if and only if (i) in Supplier’s good faith judgment, such changed or additional Specifications would not require Supplier to violate good manufacturing practice, (ii) the representation and warranty of Buyer deemed made pursuant to Subsection (e) below is true and correct, and (iii) Buyer agrees to reimburse Supplier for the incremental costs and expenses incurred by Supplier in accommodating the changed or additional Specifications, including the costs of acquiring any new machinery and tooling. For the avoidance of doubt, such costs and expenses shall be payable by Buyer separately from the cost of Products at such time or times as Supplier shall request. (d) Supplier shall notify Buyer in writing within thirty (30) days of its receipt of any request for changed or additional Specifications (i) whether Supplier will honor such changed or additional Specifications, (ii) if Supplier declines to honor such changed or additional Specifications, the basis therefor and (iii) if applicable, the estimated costs and expenses that Buyer will be required to reimburse Supplier in respect of the requested changes or additions, as provided in Subsection (c) above. Buyer shall notify Supplier in writing within fifteen (15) days after receiving notice of any required reimbursement whether Buyer agrees to assume such reimbursement obligation. (e) By its request for any changed or additional Specifications for any Product, Buyer shall be deemed to represent and warrant to Supplier that the manufacture and sale of the Product incorporating Buyer’s changed or additional Specifications, as a result of such incorporation, will not and could not reasonably be expected to (i) violate or conflict with any contract, agreement, arrangement or understanding to which Buyer and/or any of its Affiliates is a party, including this Agreement and any other contract, agreement, arrangement or understanding with Supplier and/or its Affiliates, (ii) infringe on any trademark, service xxxx, copyright, patent, trade secret or other intellectual property rights of any Person, or (iii) violate any Applicable Law. Buyer shall indemnify and hold Supplier and its Affiliates harmless (including with respect to reasonable attorneys’ fees and disbursements) from any breach of this representation and warranty.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!