# Send test failures to Slack, with the proof attached

> Connect a Slack channel, subscribe it to the projects your team owns, and get failed, blocked and inconclusive runs with what was seen and a link to the replay.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/send-test-failures-to-slack/

## Where failures should land

A failing test that emails one person on holiday is a failing test nobody reads. Most teams already have a channel where incidents get noticed. Results belong there.

## Connect a channel

From [the notifications docs](https://testsy.dev/docs/notifications/):

1. In Slack, [create an incoming webhook](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks/) for the channel that should receive results. Slack fixes the webhook to that channel.
2. In Testsy, open **Connect → Slack → Connect**, paste the webhook address and type the channel's name for reference.
3. Under **Project subscriptions**, choose **All projects** (current and future) or **Selected projects**.
4. Leave **Also post passed runs** off for failure alerts only. Click **Connect**; Testsy posts "Testsy is connected" to check delivery before saving.

Each Testsy workspace connects one Slack channel. Owners and admins manage it.

## What a message holds

Failure alerts cover failed, blocked and inconclusive runs, from every source: the web app, CI, the API, coding agents and schedules. Each includes what was seen and a link to the proof, so the person who reads it can open the replay at the failed step instead of asking "what broke?".

Runs that did not finish because of a problem on our side are left out.

## Subscribe by ownership

If the checkout team owns the checkout tests, put them in a project and subscribe only that project to the checkout channel. Selected subscriptions do not automatically include projects created later, which keeps a new experimental project from spamming a production channel.

## Keep email for the right people

Email stays on by default alongside Slack: a run started by a person emails that person; runs from a key or a schedule email the owners and admins. In **Connect → Email** you can turn either off. Every result email has a **Stop these emails** link that stops them for you alone.

## Treat the webhook like a password

Anyone with the webhook address can post to that channel. Testsy stores it encrypted and does not show it again. To move results to another channel, create a webhook for the new channel and replace the address; changing the label does not change where messages go.

For a tracker such as Linear or Jira, use a webhook of your own: [Send test results to Linear or Jira with webhooks](https://testsy.dev/blog/send-test-results-to-linear-or-jira-with-webhooks/).

This post is part of [Release testing for product teams](https://testsy.dev/blog/release-testing-for-product-teams/).
