User Testing Clause Samples

The User Testing clause establishes the requirements and procedures for evaluating a product or service by having end users interact with it before final delivery. Typically, this clause outlines the scope of testing, the responsibilities of both parties in facilitating and observing user tests, and the criteria for assessing user feedback or identifying issues. Its core function is to ensure that the product meets user needs and expectations, helping to identify and resolve usability problems before launch.
User Testing. Your end users may access the software to perform acceptance tests on your programs.
User Testing. It is your responsibility to test the functionality of Prizetech Product prior to use and to ensure that it is working and that you are able to competently operate the Prizetech Product (“User Testing”). Such User Testing must occur during normal business hours. You must respond to the email sent to you by Prizetech Pty Ltd confirming that you have conducted User Testing. You must contact Prizetech Pty Ltd if you identify any issues during User Testing and cease using the Prizetech Product until you have had a response. In no event will Prizetech Pty Ltd be liable for loss or required rescheduling if you fail to conduct User Testing in accordance with this clause.
User Testing. It will be your responsibility to test the functionality of Equipment, where provided, and the Safecrack System prior to any live draw (“User Testing”). Such User Testing must occur during normal business hours. You must respond to the email sent to you by PrizeTech Pty Ltd confirming that you have conducted User Testing. You must contact PrizeTech Pty Ltd if you identify any issues during User Testing and cease using the Safecrack until you have had a response. In no event will PrizeTech Pty Ltd be liable for loss or required rescheduling if you fail to conduct User Testing in accordance with this clause.
User Testing a. The Developer will provide capacity for the team to test hypothesis and assumptions using prototype and user research. The team will carry out user interviews and analyze competitor landscape. b. The Developer will provide capacity for the team to carry out standard usability tests running during each Sprint to test layout, content and features.
User Testing. It is your responsibility to test the functionality of Prizetech Product prior to use and to ensure that it is working and that you are able to competently operate the Prizetech Product (“User Testing”). Such User Testing must occur during normal business hours. You must respond to the email sent to you by Coverforce Insurance Broking Pty Ltd confirming that you have conducted User Testing. You must contact Coverforce Insurance Broking Pty Ltd if you identify any issues during User Testing and cease using the Prizetech Product until you have had a response. In no event will Coverforce Insurance Broking Pty Ltd be liable for loss or required rescheduling if you fail to conduct User Testing in accordance with this clause.
User Testing. SBA shall conduct semiannual user testing beginning on the execution of this Agreement to ensure that blind users can access electronic information and data in accordance with Section 508. At least one blind person experienced in 508 testing and screen reader accessibility will be engaged to conduct this user testing. SBA shall correct all Section 508 violations identified through user testing within sixty (60) days.
User Testing. Unless provided by ACM as ACM Services (as defined below), User will develop its own testing plans and provide qualified drivers, fuel, oil, engineering, and garage services for User’s vehicles (“User Provided Resources”). User agrees that neither ACM nor any employee, subcontractor, or agent of ACM will be responsible for or liable to User for any User Provided Resource and User will provide all User Provided Resources at its sole risk and expense. All User test plans are subject to a safety review by ACM personnel. Risk mitigation measures required by ACM personnel may include, but are not limited to, requiring the sole use of the test environment to be followed in order to use the Facility.
User Testing. Before E la Carte publicly releases the non-visual user interface accessibility features described above, E la Carte shall first schedule and conduct at least two user testing sessions conducted through the LightHouse for the Blind and Visually Impaired of San Francisco to test the effectiveness of the non-visual user interface. E la Carte shall pay the LightHouse $150 per user per session and an hourly honorarium agreed upon by ▇▇▇▇▇▇▇▇▇▇ and E la Carte to each user. One of these user testing sessions shall be held at the San Francisco offices of the LightHouse and one shall be held at an ▇▇▇▇▇▇▇▇’▇ location of E la Carte’s choosing unless the parties agree otherwise. LightHouse shall give preference first to ▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇ ▇▇▇▇▇, ▇▇▇▇▇▇▇ ▇▇▇▇▇▇, and ▇▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ and then to any member of the National Federation of the Blind when selecting users for testing and shall coordinate with the Office of the President of the National Federation of the Blind in identifying local candidates. E la Carte shall compile, in writing, all user feedback received through this process and share with Claimants’ Counsel. E la Carte shall make best efforts to incorporate the feedback it receives from the user testing into the development of its non- visual user interface. E la Carte shall advise Claimants’ Counsel within 21 calendar days after completion of all user testing, in writing, as to which user feedback E la Carte intends to incorporate, as well as any user feedback E la Carte does not intend to incorporate. To the extent E la Carte does not incorporate feedback, Claimants reserve the right to meet and confer with E la Carte about the feasibility of incorporating such feedback.
User Testing. With respect to Acceptance Testing, if after the initial testing period has begun, as set forth in Section 8. B. above, and if at any time during the testing period ELECT identifies defects in the required licensed functionalities of the Application, ELECT notifies the Supplier with detailed information of the defect, ELECT in consultation with Supplier, assigns severity to the defect. Defect severity is defined as follows:

Related to User Testing

  • Meter Testing Company shall provide at least twenty-four (24) hours' notice to Seller prior to any test it may perform on the revenue meters or metering equipment. Seller shall have the right to have a representative present during each such test. Seller may request, and Company shall perform, if requested, tests in addition to the every fifth-year test and Seller shall pay the cost of such tests. Company may, in its sole discretion, perform tests in addition to the fifth year test and Company shall pay the cost of such tests. If any of the revenue meters or metering equipment is found to be inaccurate at any time, as determined by testing in accordance with this Section 10.2 (Meter Testing), Company shall promptly cause such equipment to be made accurate, and the period of inaccuracy, as well as an estimate for correct meter readings, shall be determined in accordance with Section 10.3 (Corrections).

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

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

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act. (B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S. (C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.