Opening a Windows Recorder script into the Web Recorder

Any test can be opened into the Web Recorder to edit the actions and script settings supported by the Web Recorder. To open a test into the Web Recorder from the Tests page, click the Edit link in the Transaction column for the test. See Tests for more details.

Tests provisioned from scripts recorded in the Windows Recorder may be changed when they're opened into the Web Recorder, depending on their original actions and settings. If you open the test and then leave the Web Recorder without explicitly saving the test (e.g., you click the breadcrumb to go back to the Tests page), these changes are not applied to the test.

After you use the Web Recorder to edit a test provisioned from a Windows Recorder script, you can still download the test to the Windows Recorder for editing.

How the Web Recorder handles Windows Recorder actions

Not supported

These actions are not supported in the Web Recorder. If you open a test containing any of these actions into the Web Recorder, the action(s) will be removed from the test.

  • Move – This action is deprecated. You won't be warned before the action is removed.
  • Pinch and Span – A warning message is displayed that the actions will be removed if you open the test in the Web Recorder.

Fully supported

These Windows Recorder actions are fully supported by the equivalent Web Recorder actions:

  • Click
  • Cookies
  • Custom
  • File
  • Filter
  • HTTP
  • Navigate
  • Rotate
  • Scroll
  • Select
  • Swipe
  • Tap

Preserved

These actions are preserved when a Windows Recorder test is opened into the Web Recorder. However, they aren't available for new Web Recorder transactions.

  • FormFill
  • Receive SMS and Send SMS – A transaction containing these actions can't be played back in the Web Recorder.
  • Submit

Converted to equivalent functionality

These actions are converted to corresponding Web Recorder functionality:

  • Type – Converted to a Keystrokes action.
  • Validate – Shown as a Validate attribute in the preceding action.
  • Wait – Shown as a Wait attribute in the preceding action.

If a step in the Windows Recorder script begins with a Validate action, that entire step is merged with the preceding step and the Validate action becomes an attribute of the last action in the preceding step.

Example 1:

A step records a five-digit number entered in a form field as a separate Type action for each digit; each Type is followed by a Wait action. At the end of the step, submitting the form content is recorded as a Click following by a Wait. The step ends with a Validate action.

In the Web Recorder, the Type actions become five Keystrokes actions with the wait time stored as an attribute of each action. The Wait and Validate following the Click action become attributes of the Click.

Example 2:

Step 2 of a Windows Recorder script ends with a Click action, a Wait action, and a Validate action; Step 3 begins with a Validate action. Because Validate and Wait aren’t separate actions in the Web Recorder, the Wait action and the two Validate actions become attributes of the Click action, and all the other actions in Step 3 are merged into Step 2.

You can separate the merged step into two steps by clicking the action separator where you want the new step to begin, as described in Reviewing and editing a transaction.

See Validation and wait in Web recorder actions for more information.

How the Web Recorder handles Windows Recorder script settings

When a Windows Recorder test is opened into the Web Recorder, some settings may be changed because of the Web Recorder's defaults.

Profile

The script profile is imported into the Web Recorder unchanged.

If the script's User Agent String matches the default profile (for browser scripts) or the profile of a top device (for mobile scripts), that profile is displayed in the Advanced section of the Script Options page:

  • Browser – The User Agent String.
  • Mobile – The mobile device. Click Customize Device to edit the device configuration.

If the script has a custom profile, profile settings equivalent to the Windows Recorder script profile are displayed in the Advanced section of the Script Options page. You can edit these settings in the Web Recorder.

Headers

Any headers defined in the Windows Recorder script are displayed in the Headers section of the Script Options page.

Parameters

Any parameters defined in the Windows Recorder script are displayed in the Parameters section of the Script Options page.

Playback

If the Web Recorder has a default value for a playback setting, that default is applied to the transaction regardless of the original script setting. Otherwise, the original script setting is preserved.

  • Flash playback – Enabled.
  • Silverlight playback – Enabled.
  • SPDY – Enabled.
  • Include client (non-network) time in results – Enabled.
  • Run script as a repeat visitor (IE Agent only) – Original script setting (enabled or disabled) preserved.
  • IE compatibility mode – Original script setting (enabled or disabled) preserved. Not supported for playback in the Web Recorder. If this setting is enabled, it's displayed in the Advanced section of the Script Options page, and can be changed.
  • IP mode – The original setting is preserved: IPv4 only, IPv6 Only, or mixed IPv4/IPv6.

Certificate

If you've embedded a certificate in the script, it is unchanged. You can't add or revise certificates in the Web Recorder.

Hosts

The Web Recorder only supports 1-to-1 host mapping. If the script maps a host to a second or third destination, these are removed and a warning message is displayed before the script is opened into the Web Recorder.