Skip to main content
Ask AI

Slack Integration

The TestRelic Slack App brings Ask AI, scheduled QA digests, and dashboard share-back into the channels where your team already works. Type /testrelic to ask anything, pin a weekly digest to #qa-leads, or push any artifact from the web app to Slack in one click.

Growth plan required

The Slack App talks to Ask AI, which is part of the Growth plan. See Plans & Billing. The slash command will respond with a plan-upgrade prompt if your org is on Starter.

What the integration enables​

  • Slash commands in any channel — /testrelic <prompt> runs the prompt through Ask AI and threads the response under your message, with charts, deep links, and follow-up actions.
  • Scheduled QA digests — Pin recurring summaries (weekly flaky digest, Monday sprint review, nightly regression report) to any channel; cards render inline with metric tiles, top offenders, and a "View full dashboard" deep link.
  • Share-back from the web app — One click on any Ask AI artifact — dashboard, test plan, QA report, stakeholder deck — sends a rich Slack card to the channel of your choice.
  • Failure notifications — Optional alerts when monitoring quality gates fail, with the failing test case, stack trace summary, and a "Open in TestRelic" button.
  • AI-aware threading — Replies in the same thread are treated as a single Ask AI conversation, so follow-ups inherit @repo, @test_run, and other context from the original prompt.

Installing the Slack App​

  1. Open Settings → Integrations in the TestRelic web app and click Connect on the Slack card.
  2. You'll be redirected to Slack to choose the workspace and grant scopes (see Permissions).
  3. After approval, you're returned to TestRelic with the integration showing Connected.
  4. (Optional) Click Configure default channels to set channels for failure alerts and digests.
Install directly from Slack

You can also install from the Slack App Directory. The first slash command from any user will prompt them to link their Slack identity to a TestRelic account.

Permissions and scopes​

The Slack App requests these OAuth scopes:

ScopeWhy it's needed
commandsRegister the /testrelic slash command
chat:writePost threaded replies, digests, and share-back cards
chat:write.publicPost into channels the app isn't a member of (for failure alerts)
users:read.emailMatch a Slack user to their TestRelic account on first use
files:writeAttach generated reports and slides as Slack files
incoming-webhookReceive a webhook URL for the default channel chosen at install

User prompts and responses are stored in the same governed Ask AI conversation history as the web app — they are not used to train shared models.

Slash commands​

The Slack App ships a single command: /testrelic. Everything after the command name is treated as natural language, the same as the Ask AI composer.

Basic prompts​

Channel: #qa-leads
/testrelic which tests broke after yesterday's deploy?

The app replies in-thread with a regression summary card: failing test cases, the most likely root cause, affected modules, and a button to open the run in the web app.

Channel: #checkout-team
/testrelic show me the flakiest tests in the checkout suite over the last 7 days

Returns a card with a sparkline per offender, retry counts, and a "Pin as weekly digest" action.

Scoping prompts with TestRelic context​

You can use the same @ shortcuts that work in the web composer:

/testrelic summarize failures in @run-20260518-prod and tell me which are infra vs product
/testrelic generate a sprint review deck for @repo:web-app covering the last 14 days

When the response includes a presentation, report, or dashboard artifact, the app uploads it as a Slack file and posts a preview card.

Threaded follow-ups​

Replying in the thread continues the same Ask AI conversation:

/testrelic which tests broke after yesterday's deploy?
   ↳ "and which of those have been failing for more than a sprint?"
   ↳ "open a Jira ticket for the top 3"

The third message uses your connected Jira integration to file tickets without leaving Slack.

Scheduled QA digests​

Digests are recurring, AI-generated summaries that post on a cron schedule to a channel of your choice.

Creating a digest​

From the web app:

  1. Open Ask AI, run the prompt you want to schedule (e.g. "weekly flaky digest for last 7 days").
  2. In the artifact toolbar click Share → Schedule to Slack.
  3. Pick the destination channel, choose a cadence (daily / weekly / monthly), set the time and timezone, and click Schedule.

From Slack:

/testrelic schedule a weekly flaky digest to this channel every Monday 9am

Managing digests​

  • View all scheduled digests at Settings → Integrations → Slack → Schedules.
  • Pause, edit cadence, or change the destination channel inline.
  • Audit log entries record who created, paused, or deleted each schedule.

What digests look like​

Every digest is a Slack card with three sections:

  1. Headline metrics — three stat tiles (e.g. Pass Rate, Flaky %, MTTR) computed from the digest's time window.
  2. Top offenders — top 3–5 entities relevant to the prompt (flakiest tests, slowest suites, most-recent regressions), each with retry counts or trend deltas.
  3. Deep link — "View full dashboard" button that opens the equivalent Ask AI artifact in the web app, with the same time window and filters.

Share-back from the web app​

Every Ask AI artifact in the web app has a Share → Slack action.

  1. Generate the artifact in the Ask AI chat (dashboard, report, test plan, deck, or chart).
  2. Click Share → Slack in the artifact toolbar.
  3. Pick the channel and add an optional message.
  4. The card is posted with metric snapshots, a preview thumbnail (for decks and reports), and a "Open in TestRelic" deep link.

Shared cards remain queryable from Slack search and can be re-shared into other channels.

Failure alerts​

Connect monitoring quality gates to Slack to get a notification the moment a gate fails:

  1. Go to Monitoring → Quality Gates and pick a gate.
  2. Under Notifications, click Add Slack channel and select the destination.
  3. Failure alerts include the failing test case, the gate threshold that was crossed, and an Open in TestRelic button. Replies in the thread can be /testrelic prompts to ask for a root-cause analysis.

Sample use cases​

Daily standup helper​

Run during standup to anchor the conversation in real numbers:

/testrelic what's the test pass rate trend for the last 5 days, and any new flaky tests this morning?

The card surfaces three stat tiles plus a list of overnight regressions, so engineers can divide work before the meeting ends.

Triage a noisy alert​

When a quality gate alert fires:

  1. Click the Open in TestRelic button to confirm the failure is real.
  2. Reply in the alert thread: /testrelic was this flake or a real regression?
  3. The AI inspects retry patterns, comparable past failures, and CI metadata, and returns a verdict with confidence.

Sprint review one-liner​

The day before sprint review, a scheduled digest posts to #engineering-leads:

/testrelic generate a 4-slide sprint review covering test coverage, flakiest tests,
new regressions, and MTTR for the last 14 days

The card uploads the deck as a Slack file. Stakeholders read it in Slack; engineers open the artifact in TestRelic for drill-down.

Cross-team coverage check​

A PM in #growth asks a coverage question without leaving Slack:

/testrelic map critical test paths from the checkout journey to confirmation
and flag any P0 gaps for @repo:web-app

The reply renders a navigation-path map and a coverage-gap table. PM and QA align in-channel; no dashboard handoff needed.

Compliance / audit summary​

A monthly digest posts to a private compliance channel:

/testrelic generate a monthly QA evidence report covering all P0 paths,
pass-rate trends, and unresolved escapes from the @prod environment

The report is uploaded as a PDF for audit retention and linked back to the underlying TestRelic runs.

Conversation memory and privacy​

  • Slack-originated conversations show up in the Ask AI Chat Sidebar in the web app, tagged with a Slack badge.
  • Memory is scoped per TestRelic user, not per Slack user — if you trigger /testrelic from Slack and continue from the web app under the same TestRelic account, memory is continuous.
  • Channel messages from other users are not ingested unless explicitly attached as context via a future @slack-thread shortcut.

Troubleshooting​

The Slack user invoking the command isn't yet linked to a TestRelic account. Click the link in the ephemeral message to complete the OAuth match. Linking is one-time per Slack user.

Digest didn't post at the scheduled time​

Check Settings → Integrations → Slack → Schedules. Common causes:

  • The destination channel was archived or the app was removed from it. Re-add the app to the channel.
  • The org is on the Starter plan — only Growth orgs can run AI digests. The schedule pauses automatically with a notice.
  • The digest prompt failed to resolve (e.g. references a deleted repo). Edit the prompt or recreate the schedule.

"App was uninstalled" warning​

Reinstalling from Settings → Integrations → Slack → Reconnect preserves all scheduled digests and channel mappings. Tokens are rotated transparently.

Permissions error in a private channel​

The app needs to be a member of private channels to post into them. Use /invite @TestRelic in the channel, then retry the action.

Disconnecting​

  1. Navigate to Settings → Integrations.
  2. Click Disconnect on the Slack card.
  3. Confirm. All scheduled digests are paused; channel mappings are retained for 30 days in case you reconnect, then purged.

The corresponding Slack workspace admin can also revoke the app from the Slack App Management console; TestRelic will mark the integration as Disconnected the next time a webhook delivery fails.