EntityDocQuerySecuredInterfaceTest

Owned by Patrick Lobre
Last updated: Aug 30, 2019 by Eric McDonald
2 min read

EntityDocQuerySecuredInterfaceTest Details:

Overview:

EntityDocRetrieve project is used for testing Document Query functionality for the Patient IDs present in different AdhocQueryRequest elements. This project test data is populated by populateTestData.sql. In the response it is expected to display all the matching data as per AdhocQueryRequest element not as per Home Community ID (HCID)'s that are present in NhinTargetCommunities element. This test shares many similarities with the EntityDocQuery test, with the exception in that this test utilizes the Secured interfaces instead. 

Testing will be done in standard mode.


TestCase Details:

  • Document Query (G0): This test case is used to test the spec version 2.0 of the Document Query functionality for the Patient ID in AdhocQueryRequest element. When this test case is executed, a script will update UDDI connection info from project specific settings to be applied to the application server configuration and HCID endpoints are updated with test data specific to the test. When the Document Query request is processed, it returns two ExtrinsicObject elements for results of the query.  Using assertions, the script will verify the count of ExtrinsicObject to make sure expected elements are present, as well as the document ID matches the expected value.
  • Document Query (G1): This test case is used to test the spec version 3.0 of the Document Query functionality for the Patient ID in AdhocQueryRequest element. When this test case is executed, a script will update UDDI connection info from project specific settings to be applied to the application server configuration and HCID endpoints are updated with test data specific to the test. When the Document Query request is processed, it returns two ExtrinsicObject elements for results of the query.  Using assertions, the script will verify the count of ExtrinsicObject to make sure expected elements are present, as well as the document ID matches the expected value.

Preparation & Execution:

  1. Make sure to copy CONNECT common properties from \\CONNECT\Product\Production\Common\Properties\src\main\resources to application server properties folder. (If using WildFly 8.2.1 , copy into \\wildfly-8.2.1.Final\modules\system\layers\base\org\connectopensource\configuration\main).
  2. Make sure to enable Standard mode for DR service in gateway.properties. Note: By default all services will be in Standard mode in gateway.properties as of CONNECT-4.6 release.
  3. Restart application server.
  4. Deploy CONNECT ear (mvn clean install -P AD,PD,DQ,DR,DS).
  5. In SoapUI, make sure to have GatewayPropDir value set either by using global SOAPUI properties or by setting custom SOAPUI property at the project level.
  6. In SoapUI, load EntityDocQuerySecuredInterfaceTest project and execute.
  7. Make sure all test cases are passed and green.