Interface Testing. 3.5.1 Pacific and CLEC will perform interface testing as mutually agreed in the Test Plan. The parties will conduct testing on a set of interface functions for no longer than the interval specified in the Joint Testing Plan, unless a longer interval is mutually agreed to by both parties. Should the parties not agree whether a successful test was obtained within the specified interval, any disputes will be resolved pursuant to Section 4 hereof.
Interface Testing. The purpose of this test is to ensure that the usage described in Section II can be sent by PACIFIC to CLEC and can be accepted and processed by CLEC. PACIFIC will provide a test file to CLEC's designated Regional Processing Center (RPC) in the format that will be used for live day-to-day processing. The file will contain one full day's production usage. The format of the file will conform to the requirements shown in Section III. CLEC will review the file and verify that it conforms to its data center requirements. CLEC will notify PACIFIC in writing whether the format is acceptable. CLEC will also provide PACIFIC with the agreed-upon control reports as part of this test.
Interface Testing. The purpose of this test is to ensure that the usage records can be sent by U S WEST to AT&T and can be accepted and processed by AT&T. U S WEST shall provide a test file to AT&T designated Regional Processing Center (RPC) in the format that shall be used for live day-to- day processing. The file's test content and volume shall be mutually agreed to by the Parties. AT&T shall review the file and verify that it conforms to its data center requirements. AT&T shall notify U S WEST in writing whether the format is acceptable. AT&T shall also provide U S WEST with the agreed-upon control reports as part of this test.
Interface Testing. The Parties agree to usage interface testing between GTE and AT&T. The purpose of this test is to ensure that the usage described in Section II preceding can be sent by either Party and can be accepted and processed by the other Party. GTE will provide a test file to AT&T's designated Regional Processing Center (RPC) in the format that will be used for live day-to-day processing. The file will contain one (1) full day's production usage. The format of the file will conform to the requirements shown in Section III. AT&T will review the file and verify that it conforms to its data center requirements. AT&T will notify GTE in writing whether the format is acceptable. AT&T will also provide GTE with the agreed-upon control reports as part of this test. AT&T will provide a test file to GTE’s designated Regional Processing Center (RPC) in the format that will be used for live day-to-day processing. The file will contain one (1) full day's production usage. The format of the file will conform to the requirements shown in Section III. GTE will review the file and verify that it conforms to its data center requirements. GTE will notify AT&T in writing whether the format is acceptable. GTE will also provide AT&T with the agreed-upon control reports as part of this test.
Interface Testing. The main interfaces are the web server and the application server along with the database server interface. Relatively to those we checked all the interactions between these servers and they proved to be executed properly. Errors are handled properly. If database or web server returns any error message for any query by application server then application server catches and displays these error messages appropriately to users.
Interface Testing. The purpose of this test is to ensure that the usage records can be sent by U S WEST to Pac-West and can be accepted and processed by Pac-West U S WEST shall provide a test file to Pac-West designated Regional Processing Center (RPC) in the format that shall be used for live day-to-day processing. The file's test content and volume shall be mutually agreed to by the Parties. Pac-West shall review the file and verify that it conforms to its data center requirements. Pac-West shall notify U S WEST in writing whether the format is acceptable. Pac-West shall also provide U S WEST with the agreed upon control reports as part of this test.
Interface Testing. The purpose of this test is to ensure that the usage records can be sent by BellSouth to MCIm and can be accepted and processed by MCIm. BellSouth shall provide a test file to MCIm's designated Regional Processing Center (RPC) in the format that shall be used for live day-to-day processing. The file shall contain that production data which MCIm and BellSouth agree upon. MCIm shall review the file and verify that it conforms to agreed upon EMR standards. MCIm shall notify BellSouth in writing whether the format is acceptable. MCIm shall also provide BellSouth with the agreed-upon control reports as part of this test.
Interface Testing. The purpose of this test is to ensure that the Recorded Usage Data described in Section II, above, can be sent by BA to Sprint and can be accepted and processed by Sprint. BA will provide a test file to Sprint in the format that will be used for live day-to-day processing. The file will contain one (1) full day’s production usage. The format of the file will conform to the requirements shown in Section III. Sprint will review the file and verify that it conforms to the requirements shown in Section III. Sprint will notify BA in writing whether the file conforms to the requirements shown in Section III.
Interface Testing. Interface Testing is conducted to ensure the completeness of interface development and the readiness of developed interfaces for integration in the wider system. The selected Vendor shall submit its approach for Interface Testing for approval by CHFS in its Test Plan. This approach shall include strategy for early detection of interface errors such as non- conformation to interface contracts by either consumers or providers of services, and incorrect data being returned through an interface. The Interface Testing approach shall include an approach for testing of all interfaces error codes such as the network errors and unavailable source systems. The Interface Testing approach shall also outline the selected Vendor’s strategy for reporting, managing and mitigating defects for interfaces both within the control of CHFS (such as HBE) and outside the control of CHFS (such as the MCOs, PBM and Providers).
Interface Testing. The purpose of this test is to ensure that the usage described in Section II can be sent by NEVADA to CLEC and can be accepted and processed by CLEC. NEVADA will provide a test file to CLEC’s designated Regional Processing Center (RPC) in the format that will be used for live day-to-day processing. The file will contain one full day’s production usage. The format of the file will conform to the requirements shown in Section III. CLEC will review the file and verify that it conforms to its data center requirements. CLEC will notify NEVADA in writing whether the format is acceptable. CLEC will also provide NEVADA with the agreed-upon control reports as part of this test.
