Watching a test

Open any test from a scan, a flow or a break to see what Regress did and what it saw. A test that is still running fills in live.

Result

A sentence saying whether the test passed, where it stopped, or why it could not run. When a check on text or a page address fails, it shows what Regress expected and what it found.

Steps

What Regress did, as numbered steps, each with how long it took and the page it was on. Open a step to see the requests the page made during it, with each one's status and how long it took.

Recording

A picture after Regress opens a page, clicks, fills in a field or picks an option, and one where a step failed. Step through them or press play.

Timeline

The steps by kind against time, and what went wrong around them: your site's server errors, script errors on the page, and requests Regress stopped so nothing real changed.

Last time it worked

For a failed test, a picture from the same step in the last scan where this test passed, side by side.

First try

When a test failed and Regress ran it again in the same scan, switch between the two tries to see what the first one saw.

Choose Share this test to make a link that lets anyone see that test and its screenshots without signing in, for up to 30 days. The link stops working sooner if the test is deleted first, which on Free is after 7 days. It shows that one test and nothing else in your account.

When a test fails, Regress runs it once more straight away. If the second try passes, the scan reads “Passed on the second try” and no failure is reported. Tests that fill in checkout details or change records in your account are never retried. If the first try failed because your site answered with a server error and the second try worked, you hear that your site briefly failed, as a problem that can wait.

A flow that keeps needing that second try is one Regress can't trust yet, so it stops alerting on it for a while.

• A flow that needs a second try in 3 of its last 10 checks is paused. It keeps running on every scan, but its failures alert nobody. It is listed under Paused flows in the project's sidebar, with the reason.
• A paused flow that fails twice is treated as broken again and alerts as usual, so a real break waits at most one extra scan.
• After 5 clean checks in a row it comes back by itself. On daily scans that means at least 3 days of wobbling before a pause and 5 steady days before it comes back.
• Regress tells you when it pauses a flow and when it brings one back, as problems that can wait.

A test stays as long as its scan: 7 days on Free and 90 days on paid packages. Its pictures are deleted with it.