Add a site and run a first check

Add the site you test and watch {{brand}} open it in a real browser.

In short

UI Tester keeps a browser test the way a person would do it: open the site, click, type, check something is there. Add the site you test, record a test once in your browser, and {{brand}} replays it in a real browser on demand or on a schedule.

Before you start

Who: In an organization you need "Use UI Tester" (a Member holds it, a Viewer does not). On a site your level decides the rest. View opens it. Run runs ready tests. Edit changes tests and records. Manage decides where and as whom it runs.
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: a staging or test address the {{brand}} server can open, and the {{brand}} extension installed in your browser to record.

Add a site

Press + in the sites rail, or use the card shown when the workspace has no site yet.
Paste the "Site URL" - the address you test, such as your staging site. The name fills itself in; More options adds other addresses to record on, and a team.
Press "Add site". The address becomes the first address the site may record on and its first environment, the default for runs.
A Site loads test is added and run at once in a real browser, so you can watch it open your start page.

Good to know

A site is the application under test; its environments are the addresses a test runs against.
Site loads opens the start page and checks that it shows content. It is an ordinary test you can edit, schedule or archive. A site with no tests offers the same as "Check that it loads".
Recording happens in your browser through the {{brand}} extension, because only a real tab can see what you click. Replays run in your browser or from the CLI, so a pipeline can run them unattended.
Adding sites, recording, running and scheduling all need one permission, Use UI Tester. Every plan includes it.
A site made in an organization starts open to its team, or to everyone when filed under none; a site in your Personal Workspace is yours alone.
Where you may not add the sample site, the first screen leads with "Watch the demo (not saved)". See /help/ui-tester/watch-the-demo. Tests are listed under "Tests".

If something goes wrong

"Runs are unavailable": the server has no browser to replay with. Recording still works.
"A team site has to be created in an organization workspace."
Site loads fails: the server cannot reach the address. Use one the server's network can open, such as a staging site.