Note |
---|
Currently we don’t recommend running this test. This test is designed to hit the adapter layer directly and skipping out on the Entity, NwHIN, Audit, Standard and Passthrough processing. If this test being redesigned, Patient Discovery Deferred Response should be hitting the service at entity layer instead of the adapter. |
Table of Contents |
---|
Overview
Deferred Service are broken down to multiple services (Request/Response), each with it own acknowledgement. The PD Async Response (Test Project) is to verify the Response service and Acknowledgement.
Test Detail
The Bimodal test are design to hit service in standard and passthrough, by calling the JMX console to switch the service mode on the fly.
AdapterPatientDiscoveryAsyncRespTestSuite
AdapterPatientDiscoveryAsyncRespTestCase
AdapterPatientDiscoveryAsyncResp (SOAP: Patient Discovery Deferred Response)
...
Verify SOAP Response
...
Verify Receiver
...
Verify Sender
...
Overview
A deferred service is broken down to request and response, each with its own acknowledgement.
Bimodal tests are executed in both (Standard, PassThrough) modes and required JMX enable at the server level for SoapUI to successfully switch between Standard and PassThrough.
passthrough service skips out on the policy engine.
Currently the test suite is targeting Patient Discovery Deferred Response service at the adapter endpoint to verify acknowledgement response for both standard and passthrough.
Info |
---|
Currently as service (adapter) does not have standard or passthrough configuration, and the test case will switch the service over to passthrough but there no JMX to ensure the service is run in standard. Unsure if the test case is testing the right service endpoint. To test the service for standard and passthrough, it should hit the service at the entity-endpoint. |
Test Case Detail (standard and passthrough)
AdapterPatientDiscoveryAsyncRespTestCase: the test case is to verify the Patient Discovery Deferred Response (adapter) acknowledgement response.
Related To
...