Run a test and watch it

Start a run, follow it live and find past runs.

In short

Press Run to replay a test in your browser with the extension, or copy the CLI command. The step list fills with verdicts as it goes, and a step that fails keeps a screenshot.

Before you start

• Who: running a test needs Run on the site. Against Production, only people who may change the site can run unless a manager allows it.
• Plan: UI Tester is part of every plan. Every run uses browser minutes from your plan's monthly allowance (Plan & usage shows how many are left).
• First: an enabled site with an environment, and a test that is not archived and has at least one step switched on.

Start a run

1. Press "Run" on a test or its row. It queues on the default environment.
2. Or press "Run with options": pick the environment, fill in parameter values (secrets are typed for this run only) and press "Queue run".
3. The screen moves to the run straight away.

Watch it

1. Read the step list as it fills: "Passed", "Failed", "Skipped" or "Healed".
2. Select a step to see its screenshot on the right.
3. When it finishes, watch the video of the whole run. A failed run on a server shows "Console and network" too, and "Download the trace" when the run held no secret.
4. "Cancel run" stops a queued or running run; "Run again" repeats the same environment and values.

Run in your own browser

{{brand}} in the cloud does not drive a browser itself. There, Run opens a dialog with two ways to run the test, and the result is kept here the same way: it colours the test, its cards and its figures.

1. Install the {{brand}} browser extension and connect it to {{brand}}.
2. Press "Run" on a test. Pick the environment and, if the test needs them, type its secrets - they stay in this browser for this run only.
3. If the environment signs in first, choose to run its sign-in test or to use the session this browser already has.
4. Press "Run in my browser". A new tab replays the test while the dialog shows each step; "Stop" ends it after the current step.
5. When it finishes, press "Open the run". The run page shows the steps, a picture of each failed step, the first request that failed and the last lines of the console.

• "With the CLI" shows the command that runs the same test on your machine or in a pipeline; the CLI reads secrets from its own environment, never from {{brand}}.
• Runs in your browser or the CLI use no browser minutes. Their source on the runs list is "Your browser" or "CLI".
• A run that stopped before every required step was reported tells nothing about the test and is kept as Cancelled.
• The extension's own button shows the running test too: the step in hand, how each step went and "Stop the run" - handy when the run's tab covers {{brand}}.
• "Try once more after a failure" (on by default) runs a failed test again from its start. A pass on the second try is kept and marked "Flaky" on the runs list, so an unsteady test shows up.

Find past runs

Runs lists every replay, newest first, 25 to a page, with its status, steps passed, source (Manual or Schedule), start and duration. Result narrows it to Failed, Passed or Running; Test shows one test's runs. The Test health report in Analytics shows each test's pass rate over a period.

Good to know

• Run opens the options by itself when a parameter needs a value, a parameter is sensitive or the default environment is Production.
• A run needs an enabled site, a test that is not archived, an environment and at least one step switched on.
• The run uses the environment's sign-in and the site's viewport.
• Every run uses browser minutes, which are its real browser time in whole minutes, from your plan's monthly allowance. Free has 100, Pro has 1,500, Business has 1,500 per paying member shared by the organization, and Enterprise has 5,000 per member. Settings › Plan & usage shows how many are left.
• A run may take up to 20 minutes, and a step 10 seconds unless you give it a timeout.
• Run screenshots and videos are kept for 30 days; the runs and their verdicts stay.

If something goes wrong

• "An archived test cannot run." / "The test has no enabled steps to run."
• "The site has no environment to run against - add one first."
• "This site is disabled.": turn Enabled on in Site settings.
• The browser minutes are used up: the message says when they renew.

Related

• /help/ui-tester/read-a-failed-run
• /help/ui-tester/schedule-runs
• /help/analytics/report-catalog