| 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 should be redesign, Document Submission Request should be hitting the service at entity layer instead of the adapter. |
| Table of Contents |
|---|
Overview
The Test Cases are to verify Document Submission functionality: success and failure criteria; however, the verification is at adapter level.
This Test should be run at the Entity layer with standard, passthrough and spec version.
Test Detail
The Bimodal test are design to hit service in standard and passthrough, by calling the JMX console to switch the service mode without application server restart; to verify the Document Submission success and failure criteria.
XDRAdapter-Tests Suites (Standard and Passthrough)
The SOAP message are being send at the adapter (AdapterDocSubmissionUnsecured) and skipping out on all the CONNECT processing.
Success
SOAP: Success
Assert status (Success)
Success - Multiple Documents
SOAP: Success - Multiple Documents
Assert status (Success)
Failure - XDSUnknownPatientID
SOAP: Failure - XDSUnknownPatientId
Assert status (Failure)
Assert errorCode (XDSUnknownPatientId)
Assert codeContext (Patient ID referenced in metadata is not known to the Receiving NHIE)
Verify error
Failure - XDSPatientDoesNotMatch
SOAP: Failure - XDSPatientDoesNotMatch
Assert status (Failure)
Assert errorCode (XDSPatientIdDoesNotMatch)
Assert codeContext (Patient Ids do not match)
Verify error
Failure - XDSMissingDocumentMetaData
SOAP: Failure - XDSMissingDocumentMetaData
Assert status (Failure)
Assert errorCode (XDSMissingDocumentMetadata)
Assert codeContext (Unsupported Mime Type: text/xffffml)
Verify error
Failure - XDSMissingDocument
SOAP: Failure - XDSMissingDocument
Assert status (Failure)
Assert errorCode (XDSMissingDocument)
Assert codeContext (DocumentList did not contain any documents)
Verify error
Multiple Failure Messages
SOAP: Failure - XDSMissingDocument
...
Verify multiple errors
...
Assert first status (Failure)
...
Assert first errorCode (XDSMissingDocument)
...
Assert first codeContext (Document Id: Document01 exists in metadata with no corresponding attached document)
...
Assert second status (Failure)
...
Assert second errorCode (XDSUnknownPatientId)
...
Overview
The Test Suite is to verify both successful and failure criteria of Document Submission at the adapter level.
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.
| Info |
|---|
The adapter level of the application does not have standard or passthrough workflow. |
Test Cases Detail
The test cases are designed to verify successful and failure response of the Document Submission criteria at the adapter level.
Success: test case is successful with submitting a document.
Success - Multiple Documents: test case is successful with multiple documents submitted.
Failure - XDSUnknownPatientId: test case fails with unknown patient id.
Failure - XDSPatientIdDoesNotMatch: test case fails with matching patient id.
Failure - XDSMissingDocumentMetadata: test case fails with document data is missing.
Failure - XDSMissingDocument: test case fails with document missing.
Multiple Failure Messages: test case fails with multiple issues: document missing and unknown patient id.