Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml file.

Table of Contents

Overview

The Tests are designed to insert the event codes into document repository and verifying the Document Query result.

Test Detail

The Bimodal tests are designed to hit service in standard and passthrough, by calling the JMX console to switch the service mode without restarting the application server.

DQEventCodeEntryValueList

The TestCase are different in standard and passthrough mode

Standard

  • Update config: change documentQueryQuerySelf to false

  • Clear Correlation Table & Add Correlation

  • Clear AA Mapping Table & Add Mapping

PassThrough

...

TestSuite design to verify successful functionality of Document Query with slot value for Event Code. Bimodal test suite, test the service in both standard and passthrough and will call the JMX in the test case to switch service mode between standard and passthrough without application server restart.

TestCases Detail for standard and passthrough

The test cases will update document repository event code with necessary records for the Document Query to successful retrieve the specific document and event code.

Document Query in standard mode call the patient correlation service and required additional configuration for the Patient Correlation and AA Mapping.

  • DQ EventCode Entry having same Document when there are multiple slots

...

  1. ** Update config

  2. ** Clear Correlation Table & Add Correlation

  3. ** Clear AA Mapping Table & Add Mapping

  4. ** Check Passthru

  5. clear EventCode Table; Add EventCodes

  6. SOAP: Document Query

    • Assert (Document ID)

  • : the test case is setup with two event codes record and expected successful DQ to return the document as result.

  • DQ EventCode Entry one Slot having Document when there are multiple slots

...

** Update config

...

** Clear Correlation Table & Add Correlation

...

** Clear AA Mapping Table & Add Mapping

...

** Check Passthru

...

Clear EventCode Table; Add EventCodes

SOAP: Document Query

...

  • : the test case setup with one event code record and expected zero document as result.

  • DQ EventCode Entry found when there is single slot with comma separated Values

...

  1. ** Update config

  2. ** Clear Correlation Table & Add Correlation

  3. ** Clear AA Mapping Table & Add Mapping

  4. ** Check Passthru

  5. Clear EventCode Table; Add EventCodes

  6. SOAP: Document Query

    • Assert (Document ID)

  • : the test case setup with one event code record and expected successful DQ to return the document as result

  • DQ EventCode Entry found when there is single slot with multiple ValueList

...

  1. ** Update config

  2. ** Clear Correlation Table & Add Correlation

  3. ** Clear AA Mapping Table & Add Mapping

  4. ** Check Passthru

  5. Clear EventCode Table; Add EventCodes

  6. SOAP: Document Query

    • Assert (Document ID)

  • : the test case setup with one event code record and expected successful DQ to return the document as result

  • DQ EventCode Entry having same document for multiple slot with multiple ValueList

...

** Update config

...

** Clear AA Mapping Table & Add Mapping

...

** Check Passthru

...

Clear EventCode Table; Add EventCodes

SOAP: Document Query

...

  • : the test case setup with four event codes record and expected successful DQ to return the document as result

  • DQ EventCode Entry one not having same document for multiple slot with multiple ValueList

...

** Update config

...

** Clear AA Mapping Table & Add Mapping

...

** Check Passthru

...

Clear EventCode Table; Add EventCodes

SOAP: Document Query

...

  • : the test case setup with three event codes record and expected zero document as result