User Acceptance Testing (UAT. Phase in which the State tests the functionality of a Deliverable with real world scenarios to determine if the Deliverable performs in accordance with the agreed upon design as contained in the Specifications.
User Acceptance Testing (UAT. We will make the Xxxxxx Services available to you in a UAT environment. In this environment, no transactions are processed, but “test payer” User Names, Administrators and customer service representatives can access the Xxxxxx Service and perform all functions in a test environment. We will provide you with system documentation and a list of recommended UAT Test Cases. After successful execution of the test cases, you must provide a Notice of Acceptance to Bank in writing or via e-mail, whereupon the UAT shall officially end and Xxxxxx Services will be cut to live production ("Production Date") and monthly billing shall commence. The billing for the Monthly Minimum Transaction Fees shall commence on the Production Date or when live customers are using the web site, whichever comes first and shall continue throughout the term of the Agreement.
User Acceptance Testing (UAT. A. Prepare detailed UAT plans, schedules, procedures and formats.
B. Preparation and submission of detailed UAT plans/ schedules/ procedures/ formats.
C. Obtaining sign-off on testing approach and plan from the designated authority.
User Acceptance Testing (UAT. In accordance with the current Accepted Project Implementation Plan and Schedule, Agency will test the Subscription Services using both test data and Agency’s converted operational data in order to determine if the Subscription Services are in material conformance with Requirements set forth in Exhibit J, and in Deliverable ____, Functional Specifications Document, as that Deliverable is Accepted at the time of testing under this section. Agency will notify Contractor in writing of each Defect discovered during UAT in accordance with the Accepted User Acceptance Test Plan, and specify its level. Contractor shall correct all Xxxxx 0, Xxxxx 0, and Level 3 Defects identified during UAT at no additional charge to Agency, and resubmit the corrected Application to Agency for retesting within ten (10) Business Days of a written notice of Defect. All such retesting will be done on an iterative basis and be completed by Agency no later than ten (10) Business Days after Contractor submission of the corrected Application. Contractor shall correct all Xxxxx 0, Xxxxx 0, xxx Xxxxx 0 Xxxxxxx prior to completion of UAT activities under this section. Contractor shall resolve Level 4 Defects discovered during UAT at no additional charge to Agency within Agency-approved timeframes.
User Acceptance Testing (UAT. 10.1 User Acceptance Testing is primarily concerned with testing the functionality of the delivered software against the County’s business requirements and the Product Feature List provided in Appendix B-1.
10.2 The County has the primary responsibility for conducting this testing with some assistance from Contractor with process training and troubleshooting.
User Acceptance Testing (UAT. Agency will conduct UAT as set forth in this Section 6.3 and in the Statement of Work with respect to both the MVP and Phase 2 releases (each as defined in the Statement of Work). After Agency’s acceptance of the System Test Results in the applicable phase (MVP or Phase 2) and the correction of all known Xxxxx 0, Xxxxx 0, and Level 3 Defects discovered prior to UAT, Agency will test the entire System by using it in off-line processing using both test data and the Agency’s converted operational data in order to determine if the System is in material conformance with the System Requirements. Contractor shall deliver UAT Services in accordance with the UAT Task in Schedule 1. Agency will notify Contractor in writing of each Defect discovered during UAT in accordance with the Accepted Test Plan and specify its level. Contractor shall correct all Xxxxx 0, Xxxxx 0, and Level 3 Defects identified during UAT at no additional charge to Agency and resubmit the corrected System to Agency for retesting within ten (10) Business Days of a written notice of Defect. All such retesting will be done on an iterative basis and be completed by Agency no later than ten (10) Business Days after Contractor submission of the corrected System. Contractor shall correct all Xxxxx 0 Xxxxxxx, Xxxxx 0 Defects, and Level 3 Defects prior to completion of UAT activities under this section. Contractor shall resolve Level 4 Defects discovered during UAT at no additional charge to Agency within Agency- approved timeframes.
User Acceptance Testing (UAT. 1. The OPUS Project Manager and the SiVault Project Manager will determine which functions require acceptance testing before hand over. SiVault Project Manager will develop, with the assistance of OPUS, acceptance criteria.
2. OPUS will notify SiVault about its readiness for user acceptance testing.
3. SiVault shall commence UAT within 3 working days from the date of receipt of notification.
4. SiVault shall complete the UAT within 10 business days from the date of commencement of UAT.
5. Defects/shortcomings detected during UAT will be categorized as critical, to going live, and non-critical after discussion between SiVauit and OPUS.
6. OPUS will deliver the customized Electra-Card and Electra-POS after rectifying the defects or resolving the shortcomings. SiVault will complete the second cycle of UAT in not more than 5 business days from date of commencement.
7. SiVault will sign-off the acceptance document when all critical defects/shortcomings have been resolved.
8. OPUS will support the UATTeam during UAT.
9. The Team will report any defects/shortcomings to the OPUS Team.
10. OPUS will investigate and fumish remedies.
11. The UAT Team will run the UAT to ensure that OPUS has resolved the problems.
12. The UAT Team will report the successful conclusion of the UAT.
13. SiVault Project Manager and .Steering Committee will sign-off the acceptance of the system.
14. The customized Electra-Card and Electra-POS will be deemed accepted if no material defect was reported within the UAT period.
User Acceptance Testing (UAT. A testing process, performed by 4 the Program Coordinator and Program Assistant, to ensure system requirements 5 are met and understood. Upon completion of the UAT and resolution of any 6 issues, the results are shared with the Super User Group, who has the 7 responsibility to validate the acceptance of any system change(s) and/or 8 enhancement(s) to OEA.
User Acceptance Testing (UAT. Final User Acceptance Testing (UAT) shall be conducted by HDO to ensure that all functionality and requirements listed above are met.
User Acceptance Testing (UAT. The Contractor shall be responsible for providing support to the Oregon Votes Project Team during the planning and execution of UAT for both the MVP and Phase 2 releases of the System. Contractor support shall involve assistance with the following activities: • Plan and set up a UAT environment. • Provide an efficient approach to testing that maximizes parallel and overlapping test activities. • Explain how development has interpreted Requirements. • Communicate information about problems encountered during earlier test phases. • Respond to and fix reported defects. • Determine workarounds to be used during test scenario execution. • Provide information concerning the content of code builds during test execution. • Track details and provide summary reporting on testing plans, progress, issues, and interim results during test execution. The following activities have been identified as necessary to this subtask: Contractor shall: • Prepare, install, and configure the System in the UAT environment. • Coordinate all UAT environment setup activities with the Oregon Votes Project Team. • Ensure the System is properly integrated and that it is properly interfacing with all required existing external systems. • Setup, installation, and integration of the System in all locations necessary to complete UAT activities. • Maintain responsibility for System operations throughout UAT. Once the key function walkthrough has been completed with no errors, Contractor shall make the System available to the Agency and County UAT testers, who will then conduct a formal UAT of the System. Contractor shall: • Develop core functional UAT test scripts and UAT tester training materials with approval of the Agency’s PM and External QA Consultant. Test scripts must thoroughly test each functional requirement. • Develop, maintain, and refresh the UAT test environment (including database and loaded test cards). This shall be a separate environment from the production environment. • Provide System training for the UAT testers. • Provide real-time support of UAT testers. • Coordinate UAT in cooperation with theOregon Votes Project Team. • Provide an application for the capture, reporting, and tracking of errors identified during UAT. • Document UAT Results. • Fix any errors identified as a result of UAT. Contractor may be asked during the UAT to incorporate additional test scenarios, documenting their inclusion and test results. During testing, Contractor shall maintain the UAT environmen...
