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, it should interact with the DS and DR at the Entity layer. |
Overview
The test is TestSuite design to submit and query document (Registry, Repository) at adapter layer; it also query document by PatientId, DocumentUniqueId and EventCode.
Test Detail
The Bimodal test are design to hit service in standard and passthrough, by calling the JMX console to switch the service mode verify functionality of the document registry adapter.
Bimodal tests are executed in both (Standard, PassThrough) without restarting the server.
DocRegistryAndRepositoryTestSuite
Since the test is hitting the adapter layer there is no standard or passthrough; the test is design to clear the Document Repository DB, submit Document, query Document and clean up the document.
ProvideAndRegisterTest
Clear Document
SOAP: Store Document
Match response status (Success)
Delete Document
DocumentQueryTest
...
Clear Document
...
SOAP: Store Document
Match response status (Success)
...
SOAP: QueryByPatientId
Match ExternalIdentifier (CONNECT0)
Count (document)
...
SOAP: QueryByDocUniqueId
Match ExternalIdentifier (CONNECT0)
Count (document)
Verify CreationTime
Verify serviceStartTime
Verify serviceStopTime
...
SOAP: QueryByEventCode
Match ExternalIdentifier (CONNECT0)
Count (document)
Verify CreationTime
Verify serviceStartTime
Verify serviceStopTime
...
SOAP: QueryNoResults
Count (document == 0)
...
modes and required JMX enable at the server level for SoapUI to successfully switch between Standard and PassThrough.
Info |
---|
This test is calling the adapter directly and bypassed all standard and passthrough configuration of the application. |
Test Cases Detail:
ProvideAndRegisterTest: the test is looking for a successful response when provide and register a document with document registry adapter.
DocumentQueryTest: the test is to verify the document registry adapter functionality: store, query by Patient Id, Document Unique Id, Event Code and No Result Query. Successful service response for all request is expected.