EntityDocRetrieve

Owned by Tran Tang
Last updated: Aug 30, 2019 by Eric McDonald
3 min read

EntityDocRetrieve Test Suite Details:

Overview:


Important note regarding UDDIConnectionInfo.xml and internalConnectionInfo.xml

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


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 hardcoded 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.


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. 


Test Case Details:

Document Retrieve Fanout: 

This test case is used to test 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 (In this test case: 2.2 , 3.3). When Document Retrieve request is processed, it returns two DocumentResponses in RetrieveDocumentSetResponse with two attachments.  Using assertions script will verify count of DocumentResponses to make sure expected elements are present.

Document Retrieve Fanout - bad endpoint: 

This test case is used to test Document Retrieve functionality when one of the HCID's in DocumentRequest elements have wrong endpoint. 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 test case specific.  Although there are multiple HCID's in exchangeInfo.xml, script will update endpoints for only those HCID's that are present in SOAPUI request's DocumentRequest element (In this test case: 2.2 , 3.3). When DR request is processed, it returns one DocumentResponse for HCID that got a valid accesspoint with one attachment and one RegistryResponse for HCID that have wrong accesspoint in RetrieveDocumentSetResponse. There are script assertions to verify count of RegistroyError and count of DocumentResponse. 


NOTE: In both test cases although there is a HCID in NhinTargetCommunities, Document Retrieve service consider getting documents for the HCID's that are present in DocumentRequest elements. It is our understanding that HCID in NhinTargetCommunities is not required in SOAUPUI request message for this project and even if it is present it is not considered.

  • NOTE: As of CONNECT-4.6 Regression Tests are written in such a way that they work in loop back, so hostname / server name will always be local host.


It is good to run Regression scripts in gateway to gateway setup, but this is different effort and can be handled as per project priorities.


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.