Version History:
Version# | Date | Modified By | Description of Modification |
|---|---|---|---|
| 1.0 | 3/30/2016 | Sailaja Adusumilli | Initial Version |
Admin-Distribution-Standard Test Details:
Overview:
Admin-Distribution-Standard project is used to test Admin Distribution service functionality coded based on the Administrative Distribution Spec. It is accomplished by processing AD request message with EDXLDistribution metadata element. Admin Distribution service tested with or without content object element and by doing a policy check using mock policy engine service. Testing will be done in standard mode. Test case description and what it does are described below:
NOTE: As per Admin Distribution specifications, EDXL-Distribution Element does not define a response. Hence a successful response will be a standard HTTP 200 for all below test cases . Meaning, the actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
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
TestCase Details:
- EntityRequest with a Binary doc: This test case is used to test Admin Distribution service by passing a non-patient centric data binary document in content object element. When this test case is executed, an in script will first clear auditrepo.auditrepository table and generate UserId. Generated UserId will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest with XML data: This test case is used to test Admin Distribution service by passing a non-patient centric xml data in content object element. When this test case is executed, an in script will first clear auditrepo.auditrepository table and generate UserId. Generated UserId will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest with multiple documents ( XML and Binary ): This test case is used to test Admin Distribution service by passing different data formats in a content object element. When this test case is executed, an in script will first clear auditrepo.auditrepository table and generate UserId. Generated UserId will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Once request sent out and response comes in, auditing will happen and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest with multiple documents ( multiple contentObjects ): This test case is used to test Admin Distribution service using multiple content object elements with different data formats. When this test case is executed, an in script will first clear auditrepo.auditrepository table and generate UserId. Generated UserId will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest without a ContentObject tag: This test case is used to test Admin Distribution service without passing a content object element in Admin Distribution request message. When this test case is executed, an in script will first clear auditrepo.auditrepository table and generate UserId. Generated UserId will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest with an empty ContentObject: This test case is used to test Admin Distribution service by passing an empty content object element in Admin Distribution request message. When this test case is executed, an in script will first clear auditrepo.auditrepository table and generate UserId. Generated UserId will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest sent to multiple targets: This test case is used to test Admin Distribution service by sending request message to multiple target communities. When this test case is executed, an in script will first copy project level exchangeInfo.xml (which got multiple target community entries) contents into application server exchangeInfo.xml file and clear auditrepo.auditrepository table. Script will also generate UserId and it will be passed in Admin Distribution request message (Assertion-UserInfo-UserName element). Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest - Policy engine deny: This test case is used to test Admin Distribution service by failing policy check. When this test case is executed, an in script will first clear auditrepo.auditrepository table and add a mock policy engine service endpoint for given HCID in InternalconnectionInfo.xml file. Once request sent out mock policy engine service will be invoked to do a policy check. Audit will happen during request, response process and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.
- EntityRequest - 404 or 500 error: This test case is used to test Admin Distribution service by sending request message to an invalid endpoint. When this test case is executed, an in script will first clear auditrepo.auditrepository table and update Admin Distribution service endpoint to an invalid endpoint in exchangeInfo.xml file. Audit will happen during request only (as it will error out before response is processed) and audit entries will be logged into auditrepo.auditrepository table. Script will verify audit entries to make sure expected audit entries are logged in auditrepo.auditrepository table.