System Testing Clause Samples
POPULAR SAMPLE Copied 2 times
System Testing. In accordance with Agency’s written notice to proceed with System Testing, Contractor shall install and test the Enhancements on the System in the Test Environment in accordance with the System Testing Task in Exhibit A, by using it in off-line processing of test data in order to determine if the System is in material conformance with Requirements. If ▇▇▇▇▇ ▇, ▇▇▇▇▇ ▇, or Level 3 Defects are discovered in the System, Contractor shall correct such Defects and retest at no additional charge to Agency prior to completion of System Testing under this Section. Contractor shall resolve Level 4 Defects at no additional charge to Agency within Agency-approved timeframes.
System Testing. Contractor shall deliver test plans, application software and associated Documentation with each Deliverable that comply with Contractor’s test approach as described in Exhibit I, Schedule 4.1.7.
System Testing. System testing is carried out when the entire City Solution is ready. The focus of this testing is to check the behavior of the whole system as defined by the scope of the project. The main concern of system testing is to verify the system against the final business process. While performing the tests, the tester is not concerned with the internals of the system but checks if the system behaves as per expectations. This testing process is executed by the project team (City and Open) after the client configuration, integration and conversion processes are concluded.
System Testing. Upon contract execution, the Contractor shall provide a complete and comprehensive functional test plan to assure the Department of the system’s readiness to accept inmate calling traffic. This test plan shall include a checklist of items to be performed by the Contractor’s implementation team and verified by the Department’s staff.
System Testing. PBM agrees to have a testing process and corresponding written policies and procedures that are designed to identify and correct WellPoint, Plan and PBM configuration errors prior to implementation and to document the manner and extent to which it has performed such testing. PBM will provide testing results upon WellPoint’s request.
System Testing. Contractor shall develop the a test program for conducting system testing of the NEPP System (the "Test Plan"). The NEPP Test Plan is to ensure that all Equipment, Software, Interfaces, supporting hardware, Smart Media, and other System Elements furnished under this Contract meet all requirements set forth in the Contract Documents. The NEPP Test Program shall be conducted in accordance with the requirements and procedures set forth in Section 19 (Deployment, Installation And Testing) of the Technical Specification.
System Testing. An activity performed in the software development cycle in the quality assurance phase, and is completed before the release of new Releases, updates, and patches. The purpose of System Testing is to ensure that all functions and features of the Solution perform as designed, together, without Error and at acceptable performance levels. Company is responsible for System Testing, which will be performed at Company’ locations in dedicated development, support, and quality assurance environments. System Testing can also result in certification of EASE™ to run on various Third-Party required software infrastructure such as operating systems and databases.
System Testing. Subject to all applicable laws and the confidentiality obligations in this Agreement, OBH may use data capture and analysis tools to analyse data and information in an aggregated form for the purpose of monitoring and improving system performance and generating statistics and system metrics.
System Testing. Prior to LIFFE's release to the CBOT of the Software for acceptance testing, LIFFE shall test the Components. Prior to the CBOT's commencement of acceptance testing, the CBOT shall test all software required to be provided by the CBOT hereunder (the "CBOT Deliverables") to ascertain whether such software materially conforms to the CBOT's specifications for such CBOT Deliverables and those specifications for the Interfaces set forth on Schedule A. Acceptance testing shall not commence until (a) LIFFE has notified the CBOT in writing that LIFFE has reasonably determined that the Software materially conforms to the Specifications and (b) the CBOT has notified LIFFE in writing that the CBOT has reasonably determined that the CBOT Deliverables materially conforms to the CBOT's specifications for such CBOT Deliverables and those specifications for the Interfaces comprising the Specifications. Between delivery of such notice to the other Party and the CBOT's issuance of the Initial Acceptance Certificate, (i) LIFFE shall endeavor to provide the CBOT written notice of any modifications of the Software that may have a material impact on the functionality, performance or operation of the Software, and (ii) the CBOT shall endeavor to provide LIFFE written notice of any modifications to the CBOT Deliverables that may have material impact on the functionality, performance or operation of the CBOT Deliverables.
System Testing. “System Testing” shall mean the series of tests described in the SOP to determine whether all of the portions of a completed software program work together to satisfy its stated Business Requirements and Technical Specifications as set out in the BRD.