Reviewing and editing a transaction

After you record a transaction, play it back and edit it as needed before you save the test.

Play back the transaction

When you finish recording, click Playback at the top right corner of the Add Test page  to make sure the transaction plays correctly.

The actions you recorded are played back in the recording window. When playback is complete, the window closes and a message in the transaction editor tells you whether playback succeeded or failed.

Edit the transaction

When you complete the transaction, the Add Test page displays a thumbnail screenshot for each action you recorded. The actions on each web page are grouped into a step: going to a new web page creates a new step. The step name is displayed above its set of actions. To edit the step name, click the name so the text is highlighted, and type the replacement text.

Adjust step boundaries

If the default grouping of actions into steps isn't exactly what you need, you can change the step boundaries to group related actions together.

  • To split one step into separate steps, click the action separator where you want the insert the step separator.
  • To merge two steps, click the step separator between them.

Insert an action

You can add these actions to the transaction after you finish recording:

  • Custom JavaScript (Script) – Add JavaScript to the the transaction for special handling of user actions.
  • Cookie – Specify a cookie value to be used in every test execution, for consistent successful playback.
  • Navigate – Go directly to a new web page as if entering the URL in the browser's address bar.
  • File – Simulate uploading a file to the website.

To insert an action in the transaction after you finish recording:

  1. Click the plus sign  where you want to insert the action. You can add an action anywhere in the timeline, including the beginning or end.
  2. Select the action from the Insert New Action list to display the action's editing screen.
  3. Configure the action. For details, see Web Recorder Actions.
  4. Click Save at the bottom of the editing screen.
  5. Click Back to Transaction at the top of the editing screen to close the action and return to the timeline.

Edit an action

Click an action thumbnail to display its details.

In the details page, you can:

  1. Edit the action name. The default name describes the action and its target, e.g. "Navigate to <URL>" or "Click on <UI element>".
  2. If the action includes wait time, configure the wait time. For details, see Wait in Web Recorder Actions.
  3. Add a validation to confirm that the correct page loaded successfully. For details, see Validation in Web Recorder Actions.
  4. View and edit the action's Advanced Options. The available options depend on the action. For details, see Web Recorder Actions.
  5. Save the action.
    When you change the action name, the new name is saved automatically. When you change any other action details, the Save button becomes available.

Click Cancel at the bottom of the screen to undo all the changes you've made.

Click Next and Previous at the top right to move through the actions (the first action has only the Next link). Click Back to Transaction to return to the transaction timeline.

Disable an action

You can "comment out" an action by disabling it in the editing screen. For example:

  • You may have recorded an action that isn't necessary for the transaction; before deleting the action, you can disable it to make sure removing it won't affect the transaction.
  • You may want to replace an action with JavaScript in a Script action; before deleting the action the JavaScript will replace, disable it and play back the transaction to make sure the Script action performs as desired.

If you provision a test with a transaction that includes disabled actions, the disabled actions don't use XF measurements when the test runs. However, we recommend deleting any action that isn't necessary for the transaction, instead of just disabling it.

To disable an action:

  1. Click the action in the timeline to display its editing screen.
  2. Select Disabled below the action name.
  3. Save the action.

Enable an action

To re-enable a disabled action, clear the Disabled checkbox in the editing screen.

Delete an action

Caution:

You can't undo deleting an action.

  1. Open the action's editing screen.
  2. At the bottom of the screen, click Delete Action.
  3. When prompted to confirm the deletion, click OK.
    The action is deleted and you return to the transaction timeline.

Configure the script options

As of the September 2017 Web Recorder release, filters are defined in the Filter action. In transactions recorded before this release, the Exclusion Filter definitions are migrated from the Script Options page to a Filter action at the beginning of the transaction.

Click Show Settings to configure the Script Options.

The Script Options page displays the general settings for the transaction.

Caution:

Don't click Save until you have finished configuring all the options. Clicking Save automatically displays the screen to save the transaction, and you can't go back to the editing screens from that screen.

Parameters

Parameters are test-level variables that you can define in the Web Recorder and then, when needed, modify globally and by node. Using parameters ensures that the same input values are used every time the test is run, to prevent test failures.

To define parameters for the test:

  1. Click Add Parameter to display the parameter settings.
  2. Provide a Parameter name and a Default value for the parameter.
  3. Click Save New Parameter.
    The parameter is listed below the Parameters label. You can revise the parameter name or value, or Delete the parameter at any time.

After you provision the test, the parameters can be modified either in the test settings or through the Web Recorder's edit page.

Headers

When your test scenario needs HTTP request headers that aren't automatically generated by the Web Recorder, you can specify the headers in the Script Options.

  1. Click Add Header to display fields for the header.
  2. Provide a Header Name and Header Value in the fields.
  3. Click Save Header Changes.
    Repeat steps 1–3 as needed for additional headers.

Host mappings

Use host mapping to map domains that will be used by the script to specific destination IP addresses or hostnames. Host mapping causes the test to ignore the system/Internet DNS servers. You may find this useful if you are testing your network or testing a website that is not yet public.

  1. Click Add Host Mapping to display the host mapping fields.
  2. In the Hostname field, type the hostname to map.
  3. From the Map To list, select whether to map to an IP Address or Hostname.
  4. In the Destination field, type the target IP address or hostname.
  5. Click Save New Host Mapping.
    Repeat steps 1–5 as needed to create more host mappings.

Advanced

Expand the Advanced header to use these settings.

Show User Agent string

This option is available for browser transactions.

By default, the Web Recorder and Windows Recorder use the playback agent's default user agent string. Select another user agent string to emulate a supported browser version.

When you select this option, the link text changes to Hide User Agent String.

Device

The Device setting is available for mobile transactions. It displays the mobile device selected when the transaction was recorded. Click the device name to choose another device from the list of top devices.

Custom Profile

This setting is available for mobile transactions.

Click Customize Device below the Device selection to display the Custom Profile configuration.

You can change these settings:

  • Device Name – In a custom profile, this services as the profile name.
  • User Agent – By default, the user agent string is defined by the selected device.
  • Screen Width and Screen Height – You can change the display size of the device window. These settings don't affect the device orientation.
  • Device Pixel Ratio – The device pixel ratio is the ratio between logical pixels and physical pixels. It determines how a device's screen resolution is interpreted by the CSS. The device pixel ratio makes it possible to render a web page at an appropriate size regardless of the device's actual screen size. For example, if the logical resolution is 360 x 640 but a device's actual screen resolution is 720 x 1280, the device pixel ratio must be set to 2 to scale the logical resolution to the physical resolution: (720/2) x (1280/2) = 360 x 640.
    The Device Pixel Ratio is specified automatically for most devices. If necessary, you can change the value in this field.
  • Concurrent connections per host (max) – Enter the maximum number of simultaneous HTTP connections allowed to connect to a single host. The default value is 6.
  • Simultaneous HTTP requests (max) – Enter the maximum number of total requests allowed to execute at the same time. The default value is 18.

Geolocation

By default, No location is specified. You can Use the mobile node location or specify a Custom Location. For a custom location, enter the latitude (use a negative for the southern hemisphere) and longitude (negative for western hemisphere); for example, Detroit's geolocation is 42.3314 (north) latitude and -83.0458 (west) longitude.

Show Script Hints

The editing screen for an action numbers the action according to its position in the timeline; for example, the initial Navigate action is Step 01 - Action 01. However, this numbering might not be the same as the number assigned to an action in the GSL script:

  • The steps and actions are numbered in an array, beginning with zero. For example, the initial Navigate action labeled Step 01 - Action 01 in the editor is script.steps[0].actions[0] in the array.
  • When a Wait or Validate is configured for an action, the underlying script identifies the Wait or Validate as a separate action. For example, when the Navigate action (01) has a Wait configured, the next action in the timeline is labeled 02, but in the GSL script it is script.steps[0].actions[3].

Enabling Show Script Hints displays the array item corresponding to the GSL script step and action number in the action’s editing screen, for when you need to identify that specific action in JavaScript code in another Script action. Script hints are also displayed for Waits and Validations if they're configured in an action.

View HTTP Request/Response Results

After playing back an HTTP transaction, click this option to display a popup window that contains all HTTP output from the transaction.

You don't need to enable the reply handler in HTTP actions to use this option.

Show Proxy Settings

This advanced option lets you set script-level proxy settings for playback. The option should only be used for tests that will run on the [Software Private Agent]({% link_to_id id-getting-started-with-software-private-agent%}), to instruct the browser engine which proxy service to use. (You may also use it under the direction of Customer Support to override Private Last Mile’s built-in mechanism for proxy settings.). It is not supported for playback in the Web Recorder; local playback observes your Chrome browser proxy settings.

Click Show Proxy Settings to display the fields for configuring the proxy.

Use native keystrokes on playback

This advanced option may be used to for troubleshooting playback issues, on the advice of Customer Support.

View GSL script

The View GSL Script is available for all transaction types. Use this option if you need to troubleshoot the script. For details, see Exporting a Web Recorder Transaction to a File.

Save the script options

After you have finished configuring the script options

Save the transaction

When the transaction plays successfully and you have made sure the action details are correct, save the transaction to provision the tests.