TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable after the Call Off Commencement Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree) after the Call Off Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in accordance with the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the procedure to be followed if a Deliverable fails to satisfy the Test Success Criteria or produces unexpected results, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; the process for the production and maintenance of Test Reports, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues the names and contact details of the Customer's and the Supplier's Test representatives; a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and Customer and/or third party involvement in the conduct of the Tests; the technical environments required to support the Tests; and the procedure for managing the configuration of the Test environments.
TEST STRATEGY. 2.3.1 Unless otherwise agreed, EHI shall develop with the Customer a test strategy as part of the Implementation Plan, which shall include:
TEST STRATEGY. The Contact Center contingency plans strategy consists of halting one of the attendance hubs once a week (always on Sundays), it will remain shut down, the attendants are release and the calls are redirected to one of the other hubs. The hub shutdown schedule and the evidence of its performance (statistics for the day with the number of calls answered at each hub) will be the RESPONSIBILITY OF THE PARTNER (PLANNING/OPERATIONS) Training Strategy: The Call Center Training Strategy consists of a cycle of presentations made to all supervisors and managers of the three attendance hubs. This presentation is based on this document, and will be the RESPONSIBILITY OF THE PARTNER.
TEST STRATEGY. 4.1 The Supplier will develop and maintain a Test Strategy as soon as practicable after the Effective Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree in writing) after the Effective Date.
TEST STRATEGY. 3.1 The Supplier shall develop the final Test Strategy as soon as practicable but in any case no later than sixty (60) Working Days (or such other period as the Parties may agree) after the Call Off Commencement Date.
TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable after the Call Off Commencement Date but in any case no later than twenty (20) Working Days (or such other period as the Parties may agree) after the Call Off Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in relation to the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the procedure to be followed should a Deliverable fail a Test, fail to satisfy the Test Success Criteria or where the Testing of a Deliverable produces unexpected results, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; the process for the production and maintenance of Test Reports, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues the names and contact details of the Customer's and the Supplier's Test representatives; a high level identification of the resources required for Testing, including facilities, infrastructure, personnel and reports relating to such personnel, and Customer and/or third party involvement in the conduct of the Tests; the technical environments required to support the Tests; and the procedure for managing the configuration of the Test environments.
TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable but in any case no later than sixty [60] Working Days (or such other period as the parties may agree) after the Commencement Date. The final Test Strategy shall include: an overview of how Testing will be conducted in relation to the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the procedure to be followed should a Deliverable fail a Test or where a Deliverable produces unexpected results, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; and the process for the production and maintenance of reports relating to Tests.
TEST STRATEGY. 3.1 The Service Provider shall, in accordance with Schedule 3 (Milestones and Deliverables), prepare and submit to TTL a Test Strategy. As a minimum, the Test Strategy shall include:
TEST STRATEGY. The Supplier shall develop the final Test Strategy as soon as practicable after the Effective Date but in any case no later than 20 Working Days (or such other period as the Parties may agree in writing) after the Effective Date. The final Test Strategy shall include: an overview of how Testing will be conducted in accordance with the Implementation Plan; the process to be used to capture and record Test results and the categorisation of Test Issues; the method for mapping the expected Test results to the Test Success Criteria; the procedure to be followed if a Deliverable fails to satisfy the Test Success Criteria or produces unexpected results, including a procedure for the resolution of Test Issues; the procedure to be followed to sign off each Test; the process for the production and maintenance of Test Reports and reporting, including templates for the Test Reports and the Test Issue Management Log, and a sample plan for the resolution of Test Issues; the names and contact details of the Authority's and the Supplier's Test representatives;
TEST STRATEGY. Run the one-time program to generate lump sum FT transactions. For a few sample employees on the input file verify the following: • Verify that two FT transactions are generated for each employee(unless the employee is on the error report). The transaction with DOS code OTA should have the OT Premium Underpayment Amount from the input file formatted with two decimal places. The transaction LQD should have the Liquidated Amount from the input file formatted with two decimal places. See input file format below or in Attachment A of Business Requirements Document. Also the FAU should be per the ERN select in the Select statement specified. • Verify that a tab file row is generated for each employee(unless the employee is on the error report) with the correct amounts and XXXx • Verify that the employees in the error report are not found on the EDB or do not have BW pay cycle(as per the error message). Input file layout Position Field Name Description/formatting 1-23 Campus Name Campus name in quotes 24-32 Employee ID no leading zeroes, right-justified 33-34 Filler 35-62 Employee Name Employee name in quotes (L, F M) 63-74 OTP Underpayment Amt OT Premium Underpayment Amount (right-justified) 75-86 Liquidated Amount Liquidated Amount (right-justified)
