Common use of Acceptance Test Process Clause in Contracts

Acceptance Test Process. Unless otherwise agreed by the Parties, this Exhibit D describes the process used to test and accept features for inclusion on the Services (the “Acceptance Test Process”). The parties will cooperate in good faith to develop and implement communication mechanisms such that Cingular provides feedback to InfoSpace in a timely and efficient manner in order to facilitate Infospace’s ability to address such feedback. Cingular shall have the right to review and test any Deliverable to determine whether it conforms to specifications or acceptance criteria in the applicable Work Order or SOW (if any) or as otherwise agreed upon in writing by the Parties. Cingular may provide written notice of rejection (with detailed reasons for said rejection) or acceptance within the mutually agreed upon Acceptance Testing schedule from the date the Deliverable(s) are submitted by Infospace. • Following the date of delivery of a Deliverable(s) in commercial ready form (“Commercial Ready Delivery Date”), unless otherwise mutually agreed, Infospace and Cingular, prior to the beginning of test execution, will mutually agree to the following: • Schedule of test execution • Scope of test execution • Bug / Feature triage process In the event that agreed schedule must change, Infospace and Cingular will review the impact from a schedule, scope and cost perspective and will negotiate a new agreement associated with the particular Deliverable. • Following the Deliverable Acceptance Date, Infospace will commercially release the Deliverable at a mutually agreed time.