Use the following procedure to generate a REST baseline from a set of transactions in the CAI database.
You can add parameterization to REST stateful baselines. When CAI detects common elements in the request and response, it adds a property and filter to the baseline. To configure this behavior, you specify one of the following levels:
The request body must be in JSON format.
Assume that the request has the following URL and body:
If you set the parameterization level to value only, CAI considers the following elements: a, templates, 4, admin, demo_02, and 3.
If you set the parameterization level to key and value, CAI considers the following elements: user/admin, name/demo_02, and applicationId/3.
In the URL, the first element after the server and port is ignored.
Boolean types are ignored.
Follow these steps:
Click the plus sign that appears to the left of the name.
Create a baseline that contains one or more test cases that apply to an entire conversation or session, instead of simply one of its transactions. This option is not available for merged transactions.
Create a baseline that contains a single test case and a data set.
Create a baseline that contains a suite of tests (one for each transaction) and a suite document for running the tests.
The test case includes a step that corresponds to the transaction frame that you added to the shelf. For example, selecting a SOAP frame results in a test case that includes a Web Service Execution (XML) step.
The test case includes an Execute Transaction Frame step.
Converts the date strings in the baseline test case or suite to variable definition strings. For example, instead of a string that contains a specific date and time, the string can contain a function that specifies seven days from the current date and time. This behavior is equivalent to the doDateDeltaFromCurrent form of magic dates in CA Service Virtualization. If this option is unsupported, the option does not appear.