Application Testing Clause Samples

The Application Testing clause defines the procedures and requirements for evaluating software or applications to ensure they meet agreed-upon specifications and performance standards. Typically, this clause outlines the types of tests to be conducted, the responsibilities of each party during the testing phase, and the criteria for acceptance or rejection of the application. For example, it may specify timelines for testing, the process for reporting defects, and the steps for remediation. Its core function is to provide a clear framework for verifying software quality before final acceptance, thereby reducing the risk of deploying faulty or non-compliant applications.
POPULAR SAMPLE Copied 1 times
Application Testing a) At Rogers’ request, prior to ramping the production rollout, the Customer shall provide to Rogers, at no cost to Rogers, the then current application software used on the Devices (the “Application”), and associated documentation in order for Rogers to run and test such Application with the Devices to ensure network integrity and that the Application will not adversely affect Rogers Facilities or other Customers of Rogers (the “Rogers Application Testing”). b) For Applications that run on a computing platform that is physically separate from the Devices as part of the Rogers Application Testing, Customer shall also provide to Rogers the interface specifications for the Device operation. The specifications must identify standard commands and expected responses and supporting documentation. c) At Rogers’ request, Customer will provide resources, at no cost to Rogers, to assist with the Rogers Application Testing and will demonstrate to Rogers that use of the Application will not adversely affect the Rogers Facilities or other Customers of Rogers. d) Notwithstanding the Rogers Application Testing, Rogers shall not be responsible for ensuring that the Application operates or is compatible with the Rogers’ Facilities. The Customer will carry out end to end tests to ensure that the overall configuration of the Application and the Devices operate satisfactory. For initial and ongoing testing, the end to end tests shall be developed for the Devices on the application layer without using ICMP (Internet Control Message Protocol). e) Rogers may, at its discretion, continue to use the Application for on-going testing and troubleshooting purposes.
View Source
Application Testing. The Sandbox Test Environment (the “Sandbox”) is a test environment for testing Applications to ensure error-free operation prior to release. You may use information made available in the Sandbox only to develop and test your Application, and you must delete your Application from the Sandbox immediately after testing is completed.
View SourceView Similar (3)
Application Testing. IBM will perform the following test services for Applications developed or modified by IBM or for application software developed or modified by Third Party service provider(s) as set forth in Schedule F (Software):
View Source
Application Testing. TKJ Inc. has provided control samples for application testing purposes to Cyberlux Corporation. TKJ Inc has also been conducting application testing at our facilities in Northbrook for approximately 12 weeks. Information derived from the combined test results and comments from both Cyberlux and TKJ Inc shall be used to accomplish final design revisions prior to the release of the design for production. Cyberlux Corporation agrees to due diligence in application testing the products for suitability for intended use. This application testing may include use in actual final environment by end users or "field test" participants prior to any high volume production run.
View Source
Application Testing. Developer shall test the Application for use with E*TRADE System. E*TRADE reserves the right to perform, but is not obligated to perform, acceptance testing of the Application, and Developer will provide reasonable cooperation with E*TRADE should it desire to test the functions. Such testing by E*TRADE shall not create any obligations on the part of E*TRADE with respect to the Application, and Developer will not disclose in any manner to any Third-Party that E*TRADE has performed testing of the Application, or the results of any such testing undertaken by E*TRADE. The Developer will not make the functions of the Application available to End Users until the Application performs in accordance with the specifications and documentation for such Application and the functions have been tested and approved by Developer.
View Source

Related to Application Testing

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

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

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

  • Substance Abuse Testing The Parties agree that it is in the best interest of all concerned to promote a safe working environment. The Union has no objection to pre-employment substance abuse testing when required by the Employer and further, the Union has no objection to voluntary substance abuse testing to qualify for employment on projects when required by a project owner. The cost and scheduling of such testing shall be paid for and arranged by the Employer. The Union agrees to reimburse the Employer for any failed pre-access Alcohol and Drug test costs.

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