Creating a basic web services test

Browser agents provide support for monitoring web services through the HTTP Request feature.

The HTTP action enables you to define and specify the necessary requests the test should make. It works well with tests making static API calls.

These steps create a single request script. You can, however, add as many requests as necessary.

Web Recorder transaction

Open the Web Recorder.

Select > Tests, then click Add Tests at the top of the Tests page.

Select the combinations of test type and browser type, then click Continue.

Select Record a Transaction, then click Open Web Recorder.

On the Record a Transaction page, click Create Advanced Script.
The Insert New Action popup window appears.

To begin the transaction with an action that runs JavaScript and injects the result into the HTTP request, select Custom JavaScript.
Configure the action as described in Web Recorder actions.
Click Back to transaction at the top of the edit screen when you're done.

To add an HTTP action, click the add icon to the right of the Script action and select HTTP Request from the popup window.
Configure the action as described in Web Recorder actions. Best practice is to configure Wait and Validate attributes in the action.
Click Back to transaction at the top of the edit screen when you're done.

Click Playback to confirm that the transaction runs successfully.

Click Save to provision the test.
For more information, see Provisioning a Web Recorder test.

Windows Recorder script

In the Recorder, select File > New Script.
This creates a new, empty transaction. The timeline consists of one empty step.

To add a new HTTP action HTTP action, hold the mouse pointer over the action separator timeline action separator, then click the plus sign ( + ) that appears and select HTTP from the list.
The HTTP Requests tab for the action is displayed.

Edit the HTTP action.

Click the add icon Add icon to add a row to define the request for the web service call. Select the appropriate method and enter the URL.

Click More beside the row to display the Details tab in a popup window.

If you selected POST for the request, enter the POST content in the Body area.

Add any required headers for the request, if applicable.

After the HTTP action, add a Wait action Wait action.

Configure the Wait action as Wait for Network.
It is important to follow each HTTP action with a Wait for Network action to enable the agent to wait the appropriate amount of time for the request to complete.
For more information, see Wait actions.

Add a Validation action Validate action to match text within the return content to verify the script was successful.
This step is not required, but as a best practice, validations should be used throughout a transaction, especially on the final step.