Table of Contents
SoapUI
As of 5.0, the CONNECT team is testing on SoapUI 4.5.1. The change was necessitated by improvements to the Validation and Regression suites and the upgrade in CONNECT's Java to 1.7. SoapUI 4.5.1 can be downloaded here.
- For Windows, download: soapUI-x64-4.5.1.exe.
- For Unix, download: soapui-4.5.1-linux-bin.zip.
Required Jar(s)
Copy the following jar to soapui-4.5.1\lib
- FileUtils-<VERSION>-SNAPSHOT.
...
- jar
- mysql-connector-jave-5.1.10.jar
Copy the FileUtils jar from the SoapUI_Test to the soapui bin/ext lib directory.
| Code Block |
|---|
$ >copycopy C:\<4.0 clone directory>\CONNECT\Product\SoapUI_Test\FileUtils\target\FileUtils-<VERSION>-SNAPSHOT.jar C:\Users\Program Files\SmartBear\soapUI-4.5.1\bin\extlib |
Copy the MySQL Connector jar into the soapui lib directory. It is located in the maven repository (typically in your user home).
| Code Block |
|---|
$ >copycopy C:\Users\<YOU>\.m2\repositories\mysql\mysql-connector-java\5.1.10\mysql-connector-jave-5.1.10.jar C:\Users\Program Files\SmartBear\soapUI-4.5.1\lib |
Validation Suite
| Info | ||
|---|---|---|
| ||
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 |
The SoapUI projects used to validate a working CONNECT installation can be found at: <4<5.0 3 clone directory>/CONNECT/Product/SoapUI_Test/ValidationSuite.
The Validation Suite is now divided into two SoapUI projects: EntityValidation and MsgProxyValidation. The names reflect the endpoints that the tests target. Entity targets the entity and MsgProxy the message proxy endpoints. The test projects are further divided into two test suites each, g0 and g1. The g0 test suite tests the endpoints that support the specs prior to July 2011. The g1 test suite supports the endpoints that implement the July 2011 specs. To accomplish this, there are two sets of connection info that get copied into the servers nhin directory: internalExchangeInfo_g0/g1 and exchangeInfo_g0/g1.The Validation Suite tests all CONNECT services in all combinations of the spec versions (g0/g1) and gateway processing (entity/message proxy). The .
The services tested are:
- Patient Discovery
...
- Patient Discovery Deferred Request
...
- Patient Discovery Deferred Response
...
- Document Query
...
- Document Retrieve
...
- Document Submission
...
- Document Submission Deferred Request
...
- Document Submission Deferred Response
...
- Admin Distribution
- DocumentDataSubmission (disabled)
- Patient Location Query
In order to target endpoints and make configuration settings to the gateway, the NHIN config directory in the server must be know to the test project. This information is captured in a custom SoapUI property at the project level: GatewayPropDir. The property can be seen below in the SoapUI GUI.
GatewayPropDir
Alternatively, as of CONNECT 4.5.0, you can set the GatewayPropDir key/value pair in the global SoapUI properties.
The Validation Suite is now set up to be automated through maven. Directions are /wiki/spaces/CONNECTWIKI/pages/8585736here.
FileUtils
As mentioned earlier, the Validation Suite has a dependency on a utility jar named FileUtils. Upon examination of the soapui projects, you will find numerous references in the groovy scripts to nhinc.FileUtils.
...