How it works

WebTestrunner is a scheduled website testing service: you verify you own a site, configure multi-step browser checks (Playwright), and WebTestrunner runs them automatically on daily, weekly, or hourly plans.

From signup to scheduled runs

  1. Create an account — sign in with a magic link. No password to manage; use the email you want associated with the sites you monitor.
  2. Add your website — give it a name and the base URL (including https://). Goto steps resolve paths against this origin, so they stay on your site.
  3. Verify ownership — unlike a simple uptime ping, WebTestrunner only runs browser workflows on sites you prove you control. Publish a token file, meta tag, or DNS TXT record, then confirm from the dashboard. Until verification succeeds, no tests run against that site.
  4. Build a test — add Playwright steps in order. Free accounts start with a single goto path check. Paid plans unlock click, fill, and assertions so you can exercise real journeys (login, search, checkout).
  5. Schedule or run now weekly on free; daily or hourly on paid plans. You can also trigger a manual run from the dashboard anytime (subject to concurrency limits).

What a run looks like

When a test is due—or you click run—the job is queued. A runner opens headless Chromium, executes each step, and stores pass/fail results. Failed steps include an error message and screenshot artifacts so you can see what the browser saw.

Only one active run (pending or running) is allowed per test. Stale runs are cleared automatically so a stuck job does not block the next schedule.

Workflows vs uptime monitoring

Classic uptime tools ask whether a URL returns a success status. WebTestrunner asks whether a user journey still works: can the page load, can a form be filled, is the expected content still visible? That requires a real browser and domain verification—not an anonymous probe of arbitrary URLs.

Guides

Get started · View prices · About

How it works | WebTestrunner