How it works
Verify you own a site, set up multi-step journey checks, and WebTestrunner runs them automatically—weekly, daily, or hourly.
From signup to scheduled runs
- Create an account — sign in with an email link. No password to manage; use the email you want associated with the sites you monitor.
- Add your website — give it a name and the base URL (including
https://). Journey steps open paths on this origin, so they stay on your site. - Verify ownership — unlike a simple uptime ping, WebTestrunner only runs browser journeys 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.
- Build a test — add steps in order. Free accounts start with a single page visit. Paid plans unlock click, fill, and content checks so you can exercise real journeys (login, search, checkout).
- 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 real browser opens your site, follows each step, and stores pass/fail results. Failed steps include an error message and screenshot so you can see what went wrong.
Only one active run is allowed per test at a time. Stuck runs are cleared automatically so they do 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
- Verify your website — file, meta tag, or DNS
- Build browser tests — open pages, clicks, fills, content checks
- Schedules and plans — cadences and plan limits