Recorder features reference

Discover ways to share user flows, edit them and their steps in this comprehensive features reference of the Chrome DevTools Recorder panel.

To learn the basics of working with the Recorder panel, see Record, replay, and measure user flows.

# Edit user flows

On the top of the Recorder panel, there are options for you to:

1. Add a new recording. Click on the + icon to add a new recording.

2. View all recordings. The drop-down shows the list of saved recordings. Select the [number] recording(s) option to expand and manage the list of saved recordings.

3. Export a recording. To further customize the script or share it for bug reporting purposes, you can export the user flow in one of the following formats:

   • JSON file.
   • Puppeteer script.
   • @puppeteer/replay script.

   For more information on the formats, see Export a user flow.

4. Import a recording. Only in JSON format.

5. Delete a recording. Delete the selected recording.

You can also edit the recording's name by clicking the edit button next to it.

# Share user flows

You can export and import user flows in the Recorder. This is useful for bug reporting because you can share an exact record of the steps that reproduce a bug. You can also export and replay it with external libraries.

# Export a user flow

To export a user flow:

1. Open the user flow you want to export.
2. Click on the Export. button at the top of the Recorder panel.
3. Select one of the following formats from the drop-down list:
   • Export as a JSON file. Download the recording as a JSON file.
   • Export as a @puppeteer/replay script. Download the recording as a Puppeteer Replay script.
   • Export as a Puppeteer script. Download the recording as a Puppeteer script.
4. Save the file.

You can do the following with each export option:

• JSON: Edit the human-readable JSON object and import the JSON file back to the Recorder.
• @puppeteer/replay: Replay the script with the Puppeteer Replay library. When exporting as a @puppeteer/replay script, the steps remain a JSON object. This option is perfect if you want to integrate with your CI/CD pipeline but still have the flexibility to edit the steps as JSON, later convert and import them back into the Recorder.
• Puppeteer script: Replay the script with Puppeteer. Since the steps are converted into JavaScript, you can have more fine-grained customization, for example, looping the steps. One caveat, you can't import this script back into the Recorder.

# Export in a custom format by installing an extension

You can install a Chrome extension to export replay scripts in your favorite format.

For example:

• Cypress extension lets you export JSON user flows as Cypress test script. Cypress is a front end testing tool built for the modern web.
• WebPageTest extension lets you export user flows from the Recorder directly as WebPageTest Custom scripts to measure site's performance. See Converting user flows to WebPageTest custom scripts to learn more.
• Nightwatch extension lets you export JSON user flows as Nightwatch test script. Nightwatch is an end-to-end testing solution for web applications and websites.
• Testing Library extension lets you export JSON user flows as Testing Library script. Testing Library has simple and complete testing utilities that encourage good testing practices.
• WebdriverIO extension lets you export JSON user flows as WebdriverIO test script. WebdriverIO is an end-to-end testing solution for web, mobile and IoT applications and websites.

# Troubleshooting

If you don't see the export option after installing the extension, do the following:

• The extension only works on web pages. For example, the export option is not available for chrome:// pages like chrome://extensions.
• Always open a new browser tab after installing the extension.
• There is an issue in Chrome 104 and 105 that prevents the export option showing if you open the Recorder as the first DevTools panel. As a workaround, open another panel (for example, Console) first before opening the Recorder. The issue is fixed in Chrome 106.

# Import a user flow

To import a user flow:

1. Click the Import button at the top of the Recorder panel.
2. Select the JSON file with the recorded user flow.
3. Click the Replay button to run the imported user flow.

# Replay with external libraries

The Puppeteer Replay is an open source library maintained by the Chrome DevTools team. It is built on top of Puppeteer. It is a command line tool, you can replay JSON files with it.

Apart from that, you can transform and replay JSON files with the following 3rd party libraries.

Transform JSON user flows to custom scripts:

• Cypress Chrome Recorder. You can use it to convert user flow JSON files to Cypress test scripts. Watch this demo to see it in action.
• Nightwatch Chrome Recorder. You can use it to convert user flow JSON files to Nightwatch test scripts.

Replay JSON user flows:

• Replay with Testcafe. You can use TestCafe to replay user flow JSON files and generate test reports for these recordings.
• Replay with Sauce Labs. You can replay the JSON files on Sauce Labs using saucectl.

# Debug user flows

Like any code, sometimes you have to debug the recorded user flows.

To help you debug, the Recorder panel lets you slow down the replays, set breakpoints, and step through the execution.

# Slow down the replay

By default, the Recorder replays the user flow as fast as it can. To understand what happens in the recording, you can slow down the replay speed:

1. Open the Replay drop-down menu.
2. Choose one of the replay speed options:
   • Normal (Default)
   • Slow
   • Very slow
   • Extremely slow

# Set breakpoints and execute step by step

To set a breakpoint and execute step by step:

1. Hover over the circle next to any step in a recording. The circle turns into a breakpoint icon.
2. Click the breakpoint icon and replay the recording. The executions pauses at the breakpoint.
3. To step through the execution, click the Execute one step button on the action bar at the top of the Recorder panel.
4. To stop the replay, click Cancel replay.

# Edit steps

You can edit any step in the recording by clicking the button next to it.

You can also add missing steps and remove accidentally recorded ones as described below.

# Add steps

Sometimes, you may need to add steps manually. For example, the Recorder doesn't automatically capture hover events because this pollutes the recording and not all such events are useful. However, UI elements such as drop-down menus can appear only on hover. You can manually add hover steps to user flows that depend on such elements.

To manually add a step:

1. Open this demo page and start a new recording.
2. Hover over the element in the viewport. An action menu pops up.
3. Pick an action from the menu and end the recording. The Recorder captures only the click event.
4. Try to replay the recording by clicking Replay. The replay fails after a timeout because the Recorder can't access the element in the menu.
5. Click the three-dot button next to the Click step and select Add step before.
6. Expand the new step. By default, it has the waitForElement type. Click the value next to type and select hover.
7. Next, set an appropriate selector for the new step. Click Select, then click an area on the Hover over me! element that's outside the pop-up menu. The selector is set to #clickable.
8. Try replaying the recording again. With the added hover step, the Recorder successfully replays the flow.

# Copy steps

Instead of exporting the entire user flow, you can copy a single step to the clipboard:

1. Right-click the step you want to copy or click the three-dot icon next to it.
2. In the drop-down menu, select one of the Copy as ... options.

You can copy steps in various formats: JSON, Puppeteer, @puppeteer/replay, and those provided by extensions.

# Remove steps

To remove an accidentally recorded step, right-click the step or click the three-dot icon next to it and select Remove step.

Additionally, the Recorder automatically adds two separate steps to the start of every recording:

• Set viewport. Lets you control the viewport's dimensions, scaling, and other properties.
• Navigate. Sets the URL and automatically refreshes the page for every replay.

To perform in-page automation without reloading the page, remove the navigation step as described above.

# Configure steps

To configure a step:

1. Specify its type: click, doubleClick, hover, (input) change, keyUp, keyDown, scroll, close, navigate (to a page), waitForElement, waitForExpression, or setViewport.

   Other properties depend on the type value.

2. Specify the required properties below the type.

   

3. Click the corresponding buttons to add optional type-specific properties and specify them.

For a list of available properties, see Step properties.

To remove an optional property, click the Remove button next to it.

To add or remove an element to or from an array property, click the + or - buttons next to the element.

# Step properties

Each step can have the following optional properties:

• target—a URL for the Chrome DevTools Protocol (CDP) target, the default main keyword refers to the current page.
• assertedEvents that currently can only be a single navigation event

Other common properties available for most of the step types are:

• frame—an array of zero-based indexes that identify an iframe that can be nested. For example, you can identify the first (0) iframe inside a second (1) iframe of the main target as [1, 0].
• timeout—a number of milliseconds to wait before executing a step. For more information, see Adjust timeouts for steps.
• selectors—an array of selectors. For more information, see Understand selectors.

Type-specific properties are:

Type	Property	Required	Description
click doubleClick	offsetX offsetY		Relative to the top-left of the element content box, in pixels
click doubleClick	button		Pointer button: primary | auxiliary | second | back | forward
change	value		Final value
keyDown keyUp	key		Key name
scroll	x y		Absolute scroll x and y positions in pixels, default 0
navigate	url		Target URL
waitForElement	operator		>= | == (default) | <=
waitForElement	count		Number of elements identified by a selector
waitForExpression	expression		JavaScript expression that resolves to true
setViewport	width height		Width and height of the viewport in pixels
setViewport	deviceScaleFactor		Similar to Device Pixel Ratio (DPR), default 1
setViewport	isMobile hasTouch isLandscape		Boolean flags that specify whether to: Take the meta tag into account Support touch events Display in landscape mode

There are two properties that make the replay pause:

• The waitForElement property makes the step wait for the presence (or absence) of a number of elements identified by a selector. For example, the following step waits for less than three elements to be on the page that match the selector .my-class.

    "type": "waitForElement",
    "selectors": [".my-class"],
    "operator": "<=",
    "count": 2,

• The waitForExpression property makes the step wait for a JavaScript expression to resolve to true. For example, the following step pauses for two seconds and then resolves to true allowing the replay to continue.

     "type": "waitForExpression",
     "expression": "new Promise(resolve => setTimeout(() => resolve(true), 2000))",

# Adjust timeouts for steps

In case your page has slow network requests or lengthy animations, the replay can fail on steps that exceed the default timeout of 5000 milliseconds.

To avoid this problem, you can adjust the default timeout for each step at once or set separate timeouts for specific steps. Timeouts on specific steps overwrite the default.

To adjust the default timeout for each step at once:

1. Click on Replay settings to make the Timeout box editable.

   

2. In the Timeout box, set the timeout value in milliseconds.

3. Click Replay to see the adjusted default timeout in action.

To overwrite the default timeout on a specific step:

1. Expand the step and click Add timeout.

   

2. Click on the timeout: <value> and set the value in milliseconds.

   

3. Click Replay to see the step with the timeout in action.

To remove a timeout overwrite on a step, click the Delete button next to it.

# Understand selectors

When you start a new recording, you can configure the following:

• In the Selector attribute textbox, enter a custom test attribute. The Recorder will use this attribute to detect selectors instead of a list of common test attributes.

• In the Selector types to record set of checkboxes, choose the types of selectors to detect automatically:

  • CSS. Syntactic selectors.
  • ARIA. Semantic selectors.
  • Text. Selectors with the shortest unique text if available.
  • XPath. Selectors that use XML Path Language.

# Common test selectors

For simple webpages, id attributes and CSS class attributes are sufficient for the Recorder to detect the selectors. However, that might not always be the case because:

• Your webpages may use dynamic classes or IDs that change.
• Your selectors may break because of code or framework changes.

For example, the CSS class values might be auto-generated for applications developed with modern JavaScript frameworks (for example, React, Angular, Vue) and CSS frameworks.

In these cases, you can use data-* attributes to create more resilient tests. There are already some common data-* selectors that developers use for automation. The Recorder supports them as well.

If you have the following common test selectors defined on your website, the Recorder automatically detects and uses them first:

• data-testid
• data-test
• data-qa
• data-cy
• data-test-id
• data-qa-id
• data-testing

For example, inspect the "Cappuccino" element on this demo page and see the test attributes:

Record a click on "Cappuccino", expand the corresponding step in the recording, and check the detected selectors:

# Customize the recording's selector

You can customize the selector of a recording if the common test selectors don't work for you.

For example, this demo page uses the data-automate attribute as the selector. Start a new recording and enter the data-automate as the selector attribute.

Fill in an email address and observe the selector value ([data-automate=email-address]).

# Selector priority

The Recorder looks for selectors in the following order depending on if you specified a custom CSS selector attribute:

• If specified:
  1. CSS selector with your custom CSS attribute.
  2. XPath selector.
  3. ARIA selector if found.
  4. A selector with the shortest unique text if found.
• If not specified:
  1. ARIA selector if found.
  2. One of CSS selectors with the following priority:
     1. The most common attributes used for testing:
        • data-testid
        • data-test
        • data-qa
        • data-cy
        • data-test-id
        • data-qa-id
        • data-testing
     2. ID attributes, for example, <div id="some_ID">.
     3. Regular CSS selectors.
  3. XPath selector.
  4. A selector with the shortest unique text if found.