Issues and breaks

• A test that fails. One break covers that test on every page it runs on.
• Your whole site not opening: when no page Regress tries will load on two scans in a row.

A break stays one break across scans. It closes when the failing pages pass again, when Regress updates the test because your site changed, or when the test is removed or paused.

Each project's Issues page lists its open breaks with what failed, on which pages, since when and who is on it, and parts of your site that got slower. All issues, at the top of the sidebar, lists open breaks across every project you can see.

• Say you are on it, or hand it to someone. The person you hand it to gets an email.
• Add notes for whoever looks next.
• Choose “It's fixed, check now” to start a scan, or “Expected, stop telling me” to stop reminders until another page starts failing. You still hear when it is fixed.
• Open the failed test to watch it step by step. See Watching a test.

Each break records when it opens, gets worse, comes back and closes, who took it or handed it on, notes, muting, requests to check a fix, and every alert sent.

• When a break is found, when another page starts failing and when it comes back. You hear that it is fixed if you were told it was broken. A break that comes back within a day of being fixed stays quiet unless you were told it was fixed.
• A break that stays broken sends a reminder about a day, three days and a week after it started, then once a week, and nothing in between. While someone is on it, only the weekly reminders go out.

Who hears, where and when is up to your alert rules. To show breaks to your visitors, switch on a status page.