Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

EntityDocQuery Test Details:

Overview:

EntityDocQuery 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 HCID's that are present in NhinTargetCommunities element. Testing will be done in standard mode. Test case description and what it does described below:


TestCase Details:

  • Document Query Fanout: This test case is used to test 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 three ExtrinsicObject elements for results of the query.  Using assertions script will verify count of ExtrinsicObject to make sure expected elements are present.
  • Document Query Fanout - bad endpoint: This test case is used to test Document Query functionality when one of the HCID's has an invalid endpoint. 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 three ExtrinsicObject elements for results of the query, as well as one RegistryError response object.  Using assertions script will verify count of ExtrinsicObject, and the existence of the RegistryError to make sure expected elements are present.
  • Document Query SingleEndpoint: This test case is used to test Document Query functionality for the Patient ID in AdhocQueryRequest element elements. 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 a single HCID endpoint is updated with test data specific to the test. When the Document Query request is processed, it returns three ExtrinsicObject elements for results of the query.  Using assertions script will verify count of ExtrinsicObject to make sure expected elements are present.
  • Document Query State Fanout: This test case is used to test Document Query fanout functionality with use of the NhinTargetCommunities element in the entity request with a single community defined in the exchange. 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 a single HCID endpoint is updated with test data specific to the test. When the Document Query request is processed, it returns three ExtrinsicObject elements for results of the query.  Using assertions script will verify count of ExtrinsicObject to make sure expected elements are present.
  • Document Query State Fanout Multiple Communities: This test case is used to test Document Query fanout functionality with use of the NhinTargetCommunities element in the entity request with a filter on the US-VA region as well as multiple communites in the exchange configuration. 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 a single HCID endpoint is updated with test data specific to the test. When the Document Query request is processed, it returns four ExtrinsicObject elements for results of the query.  Using assertions script will verify count of ExtrinsicObject to make sure expected elements are present.

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 EntityDocQuery project and execute.
  7. Make sure all test cases are passed and green.
  • No labels