Review and edit steps

Rename, reorder and check steps, choose how each finds its element, and use parameters and secrets.

In short

After recording, review each step: rename it, reorder it, add checks, and choose how it finds its element. Parameters let one test run with different inputs, and secrets keep passwords out of every record.

Before you start

• Who: changing steps needs Edit on the site.
• Plan: every plan.
• First: record a test.

Review and edit the steps

1. Open the test. Select a step to see its recorded screenshot and its selectors.
2. Rename it, switch it off without deleting it, mark it optional, set a timeout (10 seconds by default) or edit its value.
3. Drag the handle to reorder, or use Move up and Move down in its menu.
4. Press "Add check after this step" (or "Add check here") to add a check, or "Add step" for a step by hand.

Change steps with a sentence

1. Type one sentence in "Say what to change in this test" (above the steps, and in the recorder).
2. The right dialog opens, filled in.
3. Check it and save. The sentence alone saves nothing and uses no AI answer.

Selectors

A step keeps several ways to find its element, ranked. The test id comes first. Then come the role and accessible name, label, placeholder, visible text, alt text, title and a short CSS path. XPath comes last. Replay tries them in order. When a later one succeeds the step is marked healed; "Use first", or "Promote this selector" on the run, moves it to the top. A site with test ids gives the steadiest tests.

Parameters and secrets

Parameters, on their own tab, are named inputs with defaults that a step's value uses as {{name}}. A Sensitive parameter has no default, is typed for each run and is masked in every run record.

Passwords never leave the page Anything typed into a password field, or one named like a token, card number or one-time code, is recorded as {{secret}}. To run that step, give the environment a sign-in (Sign in before runs), or declare a Sensitive parameter and type it in the run options.

Good to know

• An optional step's failure does not fail the run.
• "Delete step" keeps the records of runs that used it, and "Undo" in the message that follows puts the step back in its old place for ten minutes. A test holds at most 500 steps.
• A test that only performs proves little: add at least one check, so a run has a reason to fail.
• The step a sentence names is found by the words of its name. When several fit, they are offered to choose from.
• Changing steps needs Edit on the site.
• On the Tests list, tick several tests to set their status or delete them at once (both can be undone from the message that follows), give tests tags to filter by, switch to cards, and save the filters as a view. "Download" saves the list as a file. Above the list, the site's health shows how often its checks pass, how many passes needed a second try, how long a passing run usually takes, whether its schedules ran and how many runs happen in people's own browsers.
• A site with many tests shows them 50 to a page. Search, the chips and the sort look through every test of the site, and the chips count them all; ticked tests are the ones on the page you see.
• Two people editing the same test, step or schedule never overwrite each other: whoever saves second is asked to reload or keep their own version.

If something goes wrong

• "A test can hold at most 500 steps."
• "“secret” is kept for a password the recorder captured. Choose another name."
• The sentence box says no step fits: use more of the step's name, or the step's own menu.

Related

• /help/ui-tester/recording-a-track
• /help/ui-tester/running-and-schedules
• /help/ui-tester/read-a-failed-run