Documentation / Build browser tests

Build browser tests

A test is an ordered list of browser steps that run against one verified website. Create a test from the website page in the dashboard, then add steps.

Open a page

The open-page step (shown as goto in the dashboard) opens a path on your verified site. Enter a path starting with /—for example /login or /search?q=test—not a full URL. WebTestrunner resolves the path against your website's base URL so tests cannot wander off your domain.

Navigation must receive an HTTP 2xx status. Redirects that end in an error status fail the step.

Interact and assert

Paid plans unlock the full step set:

• click — click an element matched by a CSS selector
• fill — type a value into an input matched by a CSS selector
• assertVisible — fail if the selector is not visible
• assertText — fail if the element's text does not contain the expected string

The free tier allows a single open-page step. Use it to confirm a critical path (home, login, pricing) returns successfully each week.

Selectors

Prefer stable selectors—roles, data attributes, or dedicated test hooks—over brittle class names that change with every redesign. If a click or assertion fails, open the run detail in the dashboard to see the error and any captured screenshot.

Manual vs scheduled runs

You can trigger a run from the dashboard at any time (subject to plan concurrency limits). Scheduled runs use the cadence you set on the test. Only one active run is allowed per test at a time.

Next steps

Make sure the site is verified, then read schedules and plans to pick a cadence. Or open the dashboard.