Using CA Continuous Application Insight › Creating Baselines › webMethods Baselines › webMethods Baseline Test Cases

webMethods Baseline Test Cases

webMethods baseline test cases have a test step that reads from a Large Data data set. The test step is either a webMethods Integration Server Services step or an Execute Transaction Frame step.

If the test case has a webMethods Integration Server Services step, then the data set contains such information as the URL, request body, expected response, and response code.

If the test case has an Execute Transaction Frame step, then the data set contains the agent name, transaction frame, and expected response.

By default, the data set is local, instead of global.

The test step includes one or both of the following assertions:

• Assert Response Code Equals. When you run the baseline test case, this assertion verifies that the actual response code matches the expected response code. If the codes do not match, then the test generates an error.
• Assert Response Equals. When you run the baseline test case, this assertion verifies that the actual response value matches the expected response value. If the values 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.