Using CA Continuous Application Insight › Creating Baselines › Web Service Baselines › Web Service Baseline Test Cases

Web Service Baseline Test Cases

Consolidated web service baseline test cases have a test step that reads from a Large Data data set. The test step is either a Web Service Execution (XML) step or an Execute Transaction Frame step.

The following graphic shows an example of a consolidated web service baseline test case. The test case has a Web Service Execution (XML) step.

If the test case has a Web Service Execution (XML) step, the data set contains information such as the URL, request body, expected response, and response code. The data set can also include data from web service attachments.

If the test case has an Execute Transaction Frame step, 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 more of the following assertions:

• Assert Response Code Equals. This assertion verifies that the actual response code matches the expected response code.
• Assert Response Equals. This assertion verifies that the actual response matches the expected response. The type of assertion depends on whether the response format is XML, JSON, or raw text.

Stateful web service baseline test cases have one or more Web Service Execution (XML) steps. Each step includes the Assert Response Code Equals assertion and the Assert Response Equals assertion.

The following graphic shows an example of a stateful web service baseline test case.

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.