Using CA Continuous Application Insight › Creating Baselines › WebSphere MQ Baselines › WebSphere MQ Baseline Test Cases

WebSphere MQ Baseline Test Cases

WebSphere MQ baseline test cases have the following steps:

• A do-nothing step that reads from a Large Data data set
• A WebSphere MQ step that sends the request
• A WebSphere MQ step that receives the response

The data set contains information that changes for each transaction in the baseline. This information includes the request payload and the response payload.

In the WebSphere MQ steps, the client mode is set to native client.

The first WebSphere MQ step sends the request using data from the data set.

The second WebSphere MQ step receives the response. The step includes a Graphical XML Side-by-Side Comparison assertion with the name Assert Response Equals. When you run the baseline test case, this assertion verifies that the actual response matches the expected response. If the responses do not match, then the test generates an error.

The test case can also include a Message/Correlation ID Generator data set, which generates a 24-byte code that is used as the correlation ID.

The following graphic shows an example test case.

Binary payloads affect the structure of a WebSphere MQ baseline test case. In this scenario, the test case has the following steps:

• A do-nothing step that reads from a Large Data data set
• A Java Script step that decodes the request payload from Base64 notation into an array of bytes
• A WebSphere MQ step that sends the request
• A WebSphere MQ step that receives the response
• A Java Script step that encodes the response payload from an array of bytes into Base64 notation

The Large Data data set includes two versions of the original request payload: a human-readable version and the Base64 representation.

The Large Data data set includes two versions of the original response payload: a human-readable version and the Base64 representation.

The second Java Script step includes an assertion with the name Check Base64 Response. When you run the baseline test case, this assertion verifies that the Base64 representation of the actual response matches the Base64 representation of the expected response. If the responses do not match, then the test generates an error.

To run the test case, do one of the following actions:

• Stage a quick test
• Stage a test case

You can monitor the results in the Consolidated Baseline tab.

Note: For information about how to stage a quick test or a test case, see Running Test Cases and Suites in Using CA Application Test.