System Regression Testing Sample Clauses

System Regression Testing. The Contractor shall perform Regression Testing throughout the testing process to verify Contractor’s System integrity after functional improvements or fixes have been made as a result of Contractor’s System Integration and User Acceptance test activities. Regression testing shall be designed to confirm that fixes have not created any new problems and that the results are as planned. The results will also define the Contractor’s System baseline configuration to be released to the State. The Contractor team shall document all tests performed. It shall be the responsibility of the Contractor to ensure all automated test scripts have been assessed to ensure their proper function. The Contractor shall provide a Test Plan that includes the elements outlined above and a detailed schedule for each of the activities to be completed within the test phase, including the individuals (named and role) responsible for the completion and/or approval of each activity. Activities in the Test Plan shall include, but are not limited to: i. Definition of the Test Phase and Objectives ii. Entrance Criteria for the Test Phase iii. Exit Criteria for the Test Phase iv. Key milestones (i.e., relationship in terms of timeframes days / weeks / months, to predecessors and successor tasks) associated with each Testing Phase, including: v. Test Case Approval vi. Test Environment Readiness vii. Test Start and End dates viii. Code Baseline Configuration Established
View Source

Related to System Regression Testing

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

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

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