A recording creates multiple HTTP requests and
responses. In some cases, a response from the server can be dynamic,
because of which the subsequent requests might need to be modified.
While playing back the test, some of these dynamic requests might
fail. For example, recording and playback might involve a different
set of users with different permission settings or the UI elements
might have changed since the time you recorded the test.
To ensure that the test is played back without the need
to record it again, you can create secondary requests which, based
on the response received from the server, fetch the exact values that
the test requires .
About this task
You identify the HTTP request for which to create a secondary
request, and then create a reference for all the occurrences to dynamically
generate the request. If you do not want to create a reference, you
can define an array variable that lists the HTTP requests to use from
playback. You can use the array variable from custom code.
Procedure
- To create a reference, see the Creating a reference topic.
- Right-click the HTTP request for which to create the secondary
request and click Create Secondary HTTP Request Generator.
You can also select multiple HTTP requests that have common headers
or connection attributes. If multiple requests do not have common
attributes, you are prompted to select one request as template. The original HTTP requests are disabled, indicating that
the playback will now use only the secondary HTTP request.
- Run the test.