EntityDocRetrieveSecuredInterfaceTest

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

EntityDocRetrieveSecuredInterfaceTest Test Details:

Overview:

EntityDocRetrieve project is used for testing Document Retrieve functionality for the Home Community ID (HCID)'s present in different DocumentRequest elements. HCID can be different or it can be same with different DocumentUniqueID but RepositoryUniqueID need to be "1". (NOTE: As of CONNECT-4.6 it is our understanding that RepositoryUniqueID should always be "1" and it is a hard coded constant value that is being used while Retrieving Documents. For this project test data is populated by populateTestData.sql). In the response it is expected to display all the matching data as per DocumentRequest element not as per HCID's that are present in NhinTargetCommunities element. (NOTE: It is optional to pass HCID in NhinTargetCommunities element, even if the request have HCID, Documents will be retrieved based on the HCID's that are passed in DocumentRequest element). 

Testing will be done in standard mode.

This test is similar to the EntityDocRetrieve regression tests, but uses the Secured interfaces instead. 


TestCase Details:

  • Document Retrieve (G0): This test case is used to test the spec version 2.0 of Document Retrieve functionality for the HCID's in DocumentRequest elements. When this test case is executed an in script will update UDDI connection info data from project specific to application server configuration and HCID endpoints are updated with correct endpoints.  Although there are multiple HCID's in exchangeInfo.xml, script will update correct endpoints for only those HCID's that are present in SOAPUI request's DocumentRequest element. When Document Retrieve request is processed, it returns a single DocumentResponses in RetrieveDocumentSetResponse.  Using assertions script will verify count of DocumentResponses to make sure expected elements are present.

  • Document Retrieve (G1): This test case is used to test the spec version 3.0 of Document Retrieve functionality for the HCID's in DocumentRequest elements. When this test case is executed an in script will update UDDI connection info data from project specific to application server configuration and HCID endpoints are updated with correct endpoints.  Although there are multiple HCID's in exchangeInfo.xml, script will update correct endpoints for only those HCID's that are present in SOAPUI request's DocumentRequest element. When Document Retrieve request is processed, it returns a single DocumentResponses in RetrieveDocumentSetResponse.  Using assertions script will verify count of DocumentResponses 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 EntityDocRetrieve project and execute.
  7. Make sure all test cases are passed and green.