Overview

Testing all CONNECT services with PolicyEngineProxyConfig and verify all services response.

• Set adapterpolicyengineorchestratorjava for PolicyEngineProxyConfig with Standard

• Set adapterpolicyengineorchestratorsamljava for PolicyEngineProxyConfig with PassThrough

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 flyThe Test Suite is designed to test SAML conformance (assertion attribute statement) for policy engine for all services (G1, G0) using policy engine proxy configuration with SAML java implementation.

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.

• g1 Suite: This test suite is used to test CONNECT auditing functionality that supports the endpoints implement July-2011 specs.

• g0 Suite: This test suite is used to test CONNECT auditing functionality that supports the endpoints implement prior to July-2011 specs.

• passthrough service skip out on the policy engine.

AdapterPolicyEngineSAMLConformance

The TestSuite will include G1, G0, Standard and Passthrough.

• In passthrough, additional step is used to backup and config PolicyEngineProxyConfig.

Document Submission Deferred Req

1. ** Backup PolicyEngineProxyConfig

2. SOAP: Document Submission Deferred Request

   • Match message acknowledgement status (RequestAccepted)

   • Verify RelatesTo

Document Submission Deferred Resp

1. ** Backup PolicyEngineProxyConfig

2. SOAP: Document Submission Deferred Response

   • Match message acknowledgement status (RequestAccepted)

Document Submission

1. ** Backup PolicyEngineProxyConfig

2. SOAP: Document Submission

   • Match response status (Success)

Patient Discovery Deferred Req

1. ** Backup PolicyEngineProxyConfig

2. SOAP: Patient Discovery Deferred Request

   • Verify Receiver

   • Verify Sender

   • Verify Message

   • Verify RelateTo

Patient Discovery Deferred Resp

1. ** Backup PolicyEngineProxyConfig

2. SOAP: Patient Discovery Deferred Response

   • Match acknowledgement code (CA)

   • Match acknowledgementDetail (Success)

Patient Discovery

For PassThrough, mock-response (PDAdapter) and internalExchangeInfo.xml is update; before the request is send out.

1. clear correlations table

2. ** Backup PolicyEngineProxyConfig

3. ** Set Up PassThru

4. SOAP: Patient Discovery

   • Element exist (controlActProcess)

   • Match (Given Name)

   • Match (Family Name)

5. ** Mock Response

6. count correlations

Document Query

For the request to be successful, the data had to be updated to match the request.

1. ** Backup PolicyEngineProxyConfig

2. Clear Correlation Table & Add Correlation

3. Clear AA Mapping Table & Add Mapping

4. SOAP: Document Query

   • Match (Document ID)

Document Retrieve

1. ** Backup PolicyEngineProxyConfig

2. SOAP: Document Retrieve

   • Match (ReposityUniqueId)

   • Match (DocumentUniqueId)

   • Verify (Document Data)

Admin Distribution

...

** Backup PolicyEngineProxyConfig

...

Test Cases Detail (g1, g0, standard and passthrough)

For the following services are run in g1, g0, standard and passthrough:

• Document Submission Deferred Request

• Document Submission Deferred Response

• Document Submission

• Patient Discovery Deferred Request

• Patient Discovery Deferred Response

• Patient Discovery

• Document Query

• Document Retrieve

• Admin Distribution

Each test case verifies a successful service call and ensure the policy engine proxy is config with SAML java implementation for SAML conformance.