Where results land

Slack integration

TesterArmy posts a summary to Slack when a scheduled or webhook-triggered group run fails, with a link to each run.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Summary

What lands in the channel

The TesterArmy app posts one message per group run once the whole group finishes. The summary carries the outcome and a link to each run in the group.

Slack · TesterArmy app

TesterArmyAPP10:42

Checkout regression finished with one failure

Sign in with saved sessionView run
Add to cartView run
Apply discount codeView run
Pay with saved cardView run

When it posts
Summaries post once per group run when the whole group finishes, for Production Monitoring schedules and webhook-triggered runs.
Failures first
Failures always post, and the Notify on every run toggle adds the runs where every test passed.
Manual runs
Runs started from the dashboard, the CLI or the API never post to Slack, even when they fail.

[02] Setup

How it works

Setup is one screen under Project Settings, Integrations, Slack. To confirm the connection, trigger a scheduled or webhook group run, because a run started by hand never posts.

Add TesterArmy to Slack

In Project Settings, open Integrations, choose Slack and click Add to Slack to authorize the TesterArmy app for the workspace.

Pick the channel

On Slack's authorization screen choose the channel for alerts, and a private channel appears in the picker only when the installer is already a member.

Confirm the channel

Back in TesterArmy, confirm the integration shows the selected channel and a welcome message has landed, then decide whether Notify on every run stays off.

Read the setup docsThe docs cover setup, the Notify on every run toggle, missing notifications and changing the channel.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

Discord receives the same summaries under its own toggle. GitLab CI and any CI webhook start the group runs that notify, and Linear exports the issues found as tickets.

DiscordGroup run summaries with a link per run land in a Discord channel.GitLab CIA signed group webhook runs a test group after GitLab CI deploys.CI webhooksJenkins, Buildkite, CircleCI or a shell script triggers a group with one request.LinearIssues the agents find become Linear tickets through one shared project-wide connection.

[04] FAQ

Questions

TesterArmy posts to Slack when a Production Monitoring schedule or webhook-triggered group run fails. Pull request preview runs without a group webhook stay muted, and runs started from the dashboard, CLI or API never post.

Turning on Notify on every run posts passing group runs as well as failures. The toggle is set per channel, so Slack, Discord and email can each behave differently, and it never covers manual runs.

A private channel works when the person installing the Slack app is already a member, because that is what puts it in Slack's channel picker during authorization. Changing the channel later reopens that same flow.

TesterArmy sends one summary per group run, when the whole group finishes, for Production Monitoring schedules and webhook-triggered runs. A single test run on its own never notifies.

[05] Start with Slack

Send the next failed run to Slack

Add TesterArmy to Slack from Project Settings, pick a channel, and the next scheduled or webhook-triggered group run with a failure posts its summary there.