Web tests

A web test drives a real browser against your live site, which makes it the closest thing to a customer that Testsnag can offer. It sees what they see: rendered JavaScript, third-party scripts, real network conditions, and every redirect along the way. That fidelity is the point, and it is also why web tests are slower and more sensitive than API tests.

123

1. 1A real browser, rendering your site the way a customer sees it.
2. 2The journey, captured as ordered steps.
3. 3Run the test to replay the journey against the live site.

When to use one

Use a web test whenever the thing you care about is the experience rather than the endpoint: can somebody sign up, can they check out, does the pricing page render, does the login form actually log you in. If the question is really "does this endpoint return the right JSON", an API test will answer it faster and more reliably.

What a run collects

Every run captures a screenshot per step, browser console output, and network activity for document and XHR requests. When session recording is available on your plan, it also captures video of the whole session. Between them, most failures can be diagnosed without reproducing anything locally.

Two ways to author one

The Cloud Recorder runs the browser in Testsnag and needs nothing installed. The Browser Extension records from your own Chrome, which helps when the site is only reachable from your machine. Both produce the same steps and run the same way afterwards.