Skip to content

Help

Record or import a task

A recorded task is a task with saved steps that we replay on a schedule: one complete process a buyer would try in a demo, such as creating an invoice. Each replay captures the states it reaches, including menus, dialogs and errors the crawl cannot reach. Individual covers 2 recorded tasks, replayed weekly; Starter 5, and Team 10 on each product, replayed nightly.

Record it in Variantly

You need a paid plan and a test account.

  1. On Scope, choose Record a task and name it.
  2. Do the task on the live screenshot. Each outlined element is a button that works by keyboard and screen reader. A field asks for its value first.
  3. Choose Done to save and replay it.

Values typed into password or other secret fields are stored sealed. Nothing to install.

Import it on Scope

  1. Open your product's Scope page and go to Covered tasks, or choose Import a recording at the top of the page.
  2. Under Import recorded tasks, choose the file. You can pick up to 20 at once, 5 MB in all.
  3. Choose Import and replay. Each recorded task is replayed straight away, and its row shows when the replay finishes.
  4. Choose Open player on the row to step through the states it captured.

Importing a recorded task with the same name as one you already have replaces it. Do that when the task changes and Scope says Record again.

Record in Chrome Recorder

Record it in Chrome Recorder

  1. Open your product in Chrome and sign in with the test account you gave us, not a real person's account.
  2. Open DevTools (Ctrl Shift I, or ⌘ ⌥ I on a Mac), then the Recorder panel. If you can't see it, open the menu with the three dots and choose More tools, then Recorder.
  3. Choose Create a new recording. Name it after the task, for example "Create an invoice": the name becomes the recording's name on Scope and in the report.
  4. Choose Start recording, then do the task once, at your usual pace, from its first page to its result.
  5. Choose End recording.
  6. Choose Export, then JSON. Save the file; it ends in .json.

A recording holds what you typed. We store what goes into a password, one-time code or card field sealed, and never show it.

Playwright format reference

Or write it in Playwright

Engineers can import a Playwright test file (.ts or .js) instead. The test's title becomes the recording's name. The import reads these calls on page, in order:

  • page.goto(url) opens a page.
  • getByRole, getByLabel, getByText, getByPlaceholder or locator, followed by .click(), .fill(), .selectOption(), .press(), .hover() or .check().

Other lines, such as assertions and helpers, are skipped. Write each step as one call on page, with literal strings.

Fix an import problem

What the import refuses

When nothing is imported, Scope says why at the top of the page.

  • Choose one or more Chrome Recorder or Playwright files first. The form was sent without a file.
  • None of those files read as a Chrome Recorder or Playwright export. The file isn't a Recorder JSON export or a Playwright test, or it has no steps. Fix: export the recording again as JSON, not as Puppeteer.
  • A recorded task can open only pages on your product's site; nothing was imported. A step opens another site or an address such as file:. Fix: record the task only on your product's site.
  • Covered task limit reached. The package and Starter include 5 covered tasks, and Team includes 25 on each product. Fix: remove a recording, or re-import one with the same name to replace it.