...
Overview
The TestSuite is to verify functionality of Admin Distribution for both success and failure of the service. The TestSuite is run in passthrought, the JMX script is to ensure that the service is in passthrough without the need for server restart.
The NwHIN Administrative Distribution (AD) Web Service is intended to provide a mechanism for NHIEs to exchange non-patient specific data using a "push" mechanism. The Administrative Distribution transaction is a one way transaction, meaning there is no application-level response.
...
The AD message, also called the Send Alert Message Request, is a collection of metadata and documents or structured XML data transferred between a Message Sender and a Message Receiver.
for case 404 or 500 error, server.log must be verified.
| Table of Contents |
|---|
Overview
The Administrative Distribution (AD) service is verify by the Audit-record, that a service request had been made and audit. The test cases covers different type of data-set, that can be send by the web service (AD).
Test Detail
Administrative Distribution (Passthrough) run with JMX script configuration without application server restart.
Clear the audit-log
Send the AD Request
Verify the audit-log
Admin-Distribution-Passthrough
NHINC Proxy Request with a Binary Doc
Clear audit table
Set User ID
SOAP: NHINC Request (binary doc)
Delay 60,000 milliseconds (1 minute)
Verify audit events
NHINC Proxy Request with XML data
Clear audit table
Set User ID
SOAP: NHINC Request (XML Data)
Delay 60,000 milliseconds (1 minute)
Verify audit events
NHINC Proxy Request with multiple documents (Binary and XML)
Clear audit table
Set User ID
SOAP: NHINC Request (binary and xml)
Delay 60,000 milliseconds (1 minute)
Verify audit events
NHINC Proxy Request with multiple documents (multiple content objects)
Clear audit table
Set User ID
SOAP: NHINC Request (multiple content objects)
Delay 30,000 milliseconds (30 seconds)
Verify audit events
NHINC Proxy Request without a Content Object
Clear audit table
Set User ID
SOAP: NHINC Request (without content object)
Delay 30,000 milliseconds (30 seconds)
Verify audit events
NHINC Proxy Request with an empty Content Object
Clear audit table
Set User ID
SOAP: NHINC Request (empty content object)
Delay 60,000 milliseconds (1 minutes)
Verify audit events
NHINC Proxy Request - 404 or 500 error
Requires manual verification of the server.log for 404 or 500 error (badURL-endpoint).
...
Modify Endpoint (causing 404 or 500 error)
...
TestCases Detail for passthrough
The Test cases are used to verify Admin Distribution to handle optional element like binary document, XML metadata and content object. The service success if verify by HTTP 202 and service failure is manually verify in the server log.
NhincProxyRequest with a Binary doc: verify service with binary document
NhincProxyRequest with XML data: verify service with xml metadata
NhincProxyRequest with multiple documents (XML and Binary): verify service with both binary and xml
NhincProxyRequest with multiple documents (multiple contentObjects): verify service with populated content objects
NhincProxyRequest without a ContentObject: verify service without content objects
NhincProxyRequest with an empty ContentObject: verify service empty content objects
NhincProxyRequest - 404 or 500 error: modify the endpoint to cause 404 error and manually verify the server log is required