Email Notifications
Email notifications keep you informed about test results without requiring you to keep the DontBreak dashboard open. You can get immediate alerts when something fails, confirmations when runs pass, and a daily summary that rolls everything up — handy when you're not in Slack all day or want a record in your inbox.
Where to configure
Go to Automation > Notifications in the sidebar and select the Email tab. The panel has two parts: a master enable toggle and a list of event checkboxes.
Enable email notifications
Flip the Enable Email Notifications toggle at the top of the panel. While it's off, no emails are sent regardless of which events are checked.
Pick your events
Under Send me emails for, check the events you want delivered to your inbox.
Save
Click Save Settings. A confirmation appears when your changes are stored.
Event types
| Event | What you get |
|---|---|
| Daily summary | A once-a-day digest of your team's test activity |
| Test suite fails | An alert when a suite run finishes with failures |
| Test suite passes | A confirmation when a suite run finishes clean |
| Individual test fails | An alert when a single test fails |
| Individual test passes | A confirmation when a single test passes |
The daily summary is unique to email — it isn't available on the Slack channel. It's the lowest-noise option: even if you turn off every per-run event, the summary gives you one email a day covering how your tests did.
Tip
A common setup: Daily summary plus Test suite fails. You get an immediate email when something breaks and a daily digest for everything else, without an inbox full of pass confirmations.
How settings apply
Email notification settings are team-wide and configured only on this page. There are no per-suite or per-test email toggles — the events you check here apply to all tests and suites your team runs, including scheduled runs and runs triggered from CI/CD pipelines.
That makes scheduled monitoring a particularly good fit: if your suites run overnight on a schedule, the failure alerts and the morning daily summary tell you whether anything needs attention before your team starts the day.
Note
Pass and fail events fire per run. If a suite runs hourly on a schedule with "Test suite passes" enabled, expect an email every hour. For high-frequency schedules, stick to failure events and the daily summary.
Email vs. Slack
Both channels share the same suite and test events, so you can mirror your setup or split responsibilities:
- Email is better for the daily summary, for people who aren't in Slack, and for keeping an audit trail of failures in your inbox.
- Slack is better for real-time team response, since the alert lands in a shared channel where anyone can pick it up.
Many teams enable failure events on both: Slack for immediate triage, email as the backstop. If you also want failures turned into actionable work items automatically, connect Trello, GitHub Issues, or Jira and DontBreak will create a card or issue for each failing test.