Where results land

Discord integration

TesterArmy posts a Discord summary with a link per run when a scheduled or webhook-triggered group run fails.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Summary

What lands in the channel

The Discord bot posts a summary when a production monitoring or webhook-triggered group run finishes with a failure, carrying the group outcome and a link to each run.

Discord · TesterArmy bot

TesterArmyBOT10:42

Nightly smoke finished with one failure

Load the home pageView run
Sign in with emailView run
Search the product catalogView run
Open the billing pageView run

When it posts
A summary posts when a production monitoring or webhook-triggered group run fails, with a link to each run.
Failures first
Failures always post, and Notify on every run is set per channel, so Discord can differ from Slack.
Permissions
The bot needs to view channels, send messages and read message history in the selected server.

[02] Setup

How it works

Setup is one screen in Project Settings under Integrations, Discord. Summaries come from production monitoring and webhook-triggered group runs, so a run started by hand produces no message.

Add the bot to Discord

In Project Settings, open Integrations, choose Discord, click Add to Discord and pick the server where TesterArmy should install the bot.

Select the alert channel

Back in TesterArmy, select the channel where alerts should be posted, save it and confirm the integration shows the selected destination.

Choose what to notify

Leave Notify on every run off to hear about failures only, or turn it on to receive every run, passing ones included.

Read the setup docsConnect the bot, pick the channel, set the notify toggle, and change the channel later.

[03] FAQ

Questions

When a production monitoring or webhook-triggered group run fails, TesterArmy posts a summary to the selected channel with a link to each run. Notify on every run adds passing runs too.

A regression group triggered from any CI by its webhook posts its summary to Discord when the batch completes. Failures always post, and email is the fallback when no chat provider delivers.

Production monitoring schedules and webhook-triggered group runs post to Discord. A run started by hand from the dashboard does not, so verify the connection with a scheduled or webhook group run.

Email defaults off while a Discord channel is connected, since the chat channel already delivers alerts. Enable it under Integrations, Email to receive both. It turns back on if the chat channel is removed.

[04] Results in Discord

Hear about the next failure in Discord

Connect the bot, pick a channel, and the next failing production monitoring or webhook-triggered group run posts its summary with a link per run.