Email reports

Email reports are scheduled summaries of how a test or suite has been doing over a period: daily, weekly, or monthly. They are the right notification when you do not want a Slack ping for every run but you do want a regular check-in to confirm everything is still healthy. They land in your inbox on schedule and they link back to the relevant test or suite for any drill-down you want to do.

123

1. 1Notify when the test passes. Usually best left off.
2. 2Notify when the test fails. This is the one that matters.
3. 3Each connected integration gets its own switches for this test.

Turning them on

Enable them from the Email Reports tab in any test or suite's settings. Choose a frequency and the report will arrive on schedule with a digest of pass rate, failure count, recent runs, and trend information for the period. Each report links back to the test or suite so digging into details takes one click, and the styling is deliberately plain so it forwards cleanly to anyone who needs to see it without fighting client-specific rendering quirks.

Choosing a frequency

Daily reports work well for high-traffic critical journeys where you want a reassuring "all green for the last 24 hours" or an early warning that something started failing overnight. Weekly reports are the right cadence for most tests, providing enough signal to spot regressions without becoming a chore to read. Monthly reports suit lower-priority audits, such as SEO checks, where the absolute count of changes matters more than minute-by-minute status.

Ad-hoc reports

There is also a "Send Report Now" button if you want to email an ad-hoc summary for a specific date range. This is handy for retrospectives, for sending a manager a snapshot before a meeting, or for capturing a baseline before a release so you can compare after. The ad-hoc report uses the same template as the scheduled one, so the format stays consistent and recipients always know what they are looking at.