Test Specification Sample Clauses

Test Specification. The Test Specification represents the minimum compliance testing required for Licensed Products. Use of the Test Specification does not guarantee that any product will conform to the PWG Specification, function correctly or interoperate with any other product. Licensee acknowledges that it shall be Licensee’s sole responsibility to establish its own testing specifications, guides and reference designs to establish conformance with the PWG Specifications’ correct functionality and interoperability. Licensee shall be solely responsible for all test results and acknowledges and agrees that the LLA shall not be liable in any manner for any test results or the sufficiency or appropriateness of the Test Specification.
AutoNDA by SimpleDocs
Test Specification. (i) U3 and any other ASIC Product that the parties may agree to treat in a similar manner: Apple shall define and implement its own design verification tests, which testing activities shall be no less thorough than those testing activities generally conducted by Apple but not less thorough than those testing activities generally conducted by other personal computer manufacturers (but not microprocessor manufacturers) in the industry (receipt by IBM of Apple’s Prototype Acceptance as set forth in the ASIC Development Agreement, Agreement No. 000798 shall establish that the Prototype design revision conformed with the agreed-upon specifications as set forth in the RTM); and (ii) other Exhibit 4 Products: Apple and IBM shall agree on a test specification that shall set forth the minimum level of testing of the other Exhibit 4 Products sold hereunder both (a) by IBM prior to shipment from IBM to Apple and (b) by Apple prior to shipment to end-user customers, and other matters such as a returned-parts process and regular communications expected between the parties. Either party shall be free to exceed the agreed-upon level of testing.
Test Specification. 7.1 As part of the Test Plan, the Supplier shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan). 7.2 Each Test Specification shall include as a minimum: 7.2.1 7.
Test Specification. 7.1 Following approval of a Test Plan, the Service Provider shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least 10 Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan). For routine, planned updates and any updates being made as a result of approved Change Requests during the Term, Test Specifications may be developed and agreed by both Parties, in line with the test strategy. 7.2 Each Test Specification shall include as a minimum: (a) a mechanism for tracking traceability of Tests being conducted to requirements; (b) Test cases or scripts; (c) Test pre-requisites and the mechanism for measuring them; and (d) expected Test results.
Test Specification. During the test specification phase, the test cases are specified. It consists of description of the input, process to be executed and a prediction of output results.
Test Specification. Following approval of a Test Plan, the Supplier shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least 10 Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan). Each Test Specification shall include as a minimum: the specification of the Test data, including its source, scope, volume and management, a request (if applicable) for relevant Test data to be provided by the Authority and the extent to which it is equivalent to live operational data;
Test Specification. Mainly based on the functional characteristics of the original replacement thick film circuit.
AutoNDA by SimpleDocs
Test Specification. 7.1 Following approval of the Test Plan, the Service Provider shall develop the Test Specification for the relevant Deliverables as soon as reasonably practicable and in any event at least ten (10) Working Days (or such other period as the Parties may agree in the Test Strategy or otherwise agree in writing) prior to the start of the relevant Testing (as specified in the Implementation Plan). 7.2 Each Test Specification shall include as a minimum: 7.2.1 the specification of the Test data, including its source, scope, volume and management, a request (if applicable) for relevant Test data to be provided by UK Biobank and the extent to which it is equivalent to live operational data; 7.2.2 a plan to make the resources available for Testing; 7.2.3 Test scripts; 7.2.4 Test pre-requisites and the mechanism for measuring them; and 7.2.5 expected Test results including: 7.2.5.1 a mechanism to be used to capture and record Test results; and 7.2.5.2 a method to process the Test results to establish their content

Related to Test Specification

  • 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.

  • 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.

  • 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.

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