Skip to main content
A TestSprite run summary posted in a Slack channel
TestSprite can post a summary to your Slack workspace every time a test run completes, so your team sees results the moment they land — without anyone checking the dashboard. It works for every kind of run: manual, scheduled, GitHub-triggered, or started from the CLI. Setup happens in two places:
  1. Connect Slack once per workspace — links your TestSprite workspace to a Slack workspace (workspace Owner/Admin only).
  2. Pick a channel per project — each project chooses its own channel and switches notifications on or off independently.
Slack notifications are available on every plan. Connecting and disconnecting Slack requires the workspace Owner or Admin role.

​
Step 1 — Connect Slack (once per workspace)

Workspace Integrations page with the Slack row
1

Open Integrations

In your workspace settings, go to Workspace Settings → Connections → Integrations and click the Slack row, then Connect With Slack.
2

Authorize TestSprite

A Slack authorization window opens. Approve the requested permissions — TestSprite asks only for what it needs to list channels and post messages:
3

Done — the workspace is linked

Back in TestSprite, the Slack page shows Connected Workspace with your Slack team’s name. One Slack workspace is linked per TestSprite workspace; every project in it can now pick a channel.

​
Step 2 — Choose a Channel for Each Project

Notifications & Ticketing settings with the Slack channel picker open
1

Open the project's notification settings

In the project’s sidebar, go to Project Settings → Notifications & Ticketing. The Slack card shows the connected workspace.
2

Pick a channel

Under Channel, select where summaries should be posted. Public channels appear as #channel-name; private channels show a lock icon.
3

Turn on notifications and save

Enable Notify on test run completion and click Save changes. From now on, every completed run of this project posts a summary to that channel.

​
Public vs. Private Channels

Private channels require one extra step. The TestSprite bot cannot see a private channel until it is invited. In Slack, open the private channel and run /invite @TestSprite first — the channel won’t appear in TestSprite’s channel list until you do. After inviting, switch back to the TestSprite tab and the list refreshes automatically.
Inviting the bot takes a few seconds. In the private channel, type /invite and choose Invite someone to this channel:
Typing /invite in a private Slack channel and choosing Invite someone to this channel
Then search for the TestSprite app and add it:
Selecting the TestSprite app in Slack's Add people dialog

​
What You’ll Receive

A summary is posted once per completed test run — whether the run was started manually, by a schedule, by a GitHub event, or from the CLI. There is currently no “failures only” filter; if the project’s toggle is on, every run reports.

​
What’s in a Notification Card

Choosing channels well beats filtering. Since every run posts, route noisy projects (frequent scheduled runs) to a dedicated channel like #testsprite-monitoring, and keep release-critical projects in your team channel where a failure gets seen immediately.

​
Change Channel, Disable, or Disconnect

  • Change a project’s channel or turn its notifications off: back in the project’s Project Settings → Notifications & Ticketing, pick a different channel or flip Notify on test run completion off, then Save changes.
  • Disconnect Slack from the whole workspace: go to Workspace Settings → Connections → Integrations → Slack and click Disconnect (Owner/Admin only). All projects stop posting immediately.
Disconnecting keeps each project’s channel choice. If you reconnect the same Slack workspace later, projects resume posting to their previously selected channels.

​
Troubleshooting

The bot hasn’t been invited yet. In Slack, open the channel and run /invite @TestSprite, then return to the TestSprite tab — the list refreshes when the tab regains focus.
Check three things in order: the project’s Notify on test run completion toggle is still on; the workspace’s Slack connection still shows Connected under Workspace Settings → Connections → Integrations; and, for a private channel, the @TestSprite bot is still a member (a bot removed from the channel fails silently).
Connecting requires the workspace Owner or Admin role. Members don’t see Integrations at all.

​
Where to Go Next

Ticketing

Turn failed tests into tickets automatically

Test Schedules

Set up scheduled runs that report to Slack