ExchangeManager

Overview:

ExchangeManager project is used for testing the exchange manager functionality for all the current services in CONNECT. This test ensures that a default exchange can be overridden using the nhinTargetCommunities element. In both testing configurations, the default exchange provided has no endpoints available for the services, and would otherwise fail to be invoked if the exchange is not overridden with the exchange targeting functionality of the Exchange Manager.

Testing will be done in standard mode. 

Each test here runs through roughly the same steps, so the test case will be explained as a whole from a general standpoint.

Each test here runs through the general process of clearing out the event logging table to ensure the counts of each invocation is correct. Once the table is cleared, the respective service will be invoked with mock data. This data is populated via setup scripts according to the service being run. Additional scripts/configuration may be setup in instances such as Document Submission (DS) and Document Query (DQ) tests where a correlation is inserted for mock data as well. After the service is invoked, we then check the eventdb table for the correct number of entries, and ensure each BEGIN_* entry has its respective END_* element. It also ensures that these entries have the correct service name listed in the event row.