Overview
The Slack App sends notifications that you build per project. Each notification picks its own Slack channels and people and fires on its own trigger. Start from a type such as Test failures or Flaky tests, then edit any field.
Scope a notification to certain branches or environments so production failures reach one channel and staging results reach another. Tag-based and annotation-based notifications reach the owner of a test, including a direct message to the person named in a testdino:notify-slack annotation.
Key features
- Multiple notifications per project, each with its own destinations
- Channels and people in the same notification
- Branch and environment filters per notification
- Annotation-based direct messages to test owners
- Live preview and Send test before you rely on it
- Available on Pro, Team, and Enterprise plans
How it works
Connect Slack
In Project, then Integrations, click Connect Slack App and complete the OAuth flow. Or find and install TestDino from the Slack App Marketplace.
Add a notification
Click Configure on Notification rules, pick a type, and choose the Slack channels and people it goes to. A live preview shows the exact message as you edit.
Save and send a test
Save the notification, then click Send test to post a real message to every destination on it.
One integration, as many notifications as you need
Choose when a notification sends: only when the run fails, when it fails or has flaky tests, every time a run finishes, or only when it passes. Choose which tests it lists, from failed only to every test, with 1 to 25 rows per message.
Limit a notification to tests with certain tags, or skip tagged tests, and restrict it to certain branches or environments. Add run details such as the pull request, commit author, CI job, or environment to the message.