Introducing the TestRelic Slack App: /testrelic, scheduled QA digests, and share-back from Ask AI

Today we're launching the TestRelic Slack App — a way to bring Ask AI, scheduled QA digests, and dashboard share-back directly into the channels where your team already works. Type /testrelic in any channel to ask anything, schedule a weekly flaky digest to #qa-leads, or push any artifact from the web app to Slack in one click.

Why a Slack app

Most teams already have a Slack channel where QA, engineering, and on-call meet. Until today, getting a test answer into that channel meant: open the web app, navigate, screenshot, paste. Three steps too many.

We watched our own team and a handful of design partners do this dozens of times a week. The right answer wasn't another dashboard — it was making Ask AI reachable from inside the conversation. So we built it.

The Slack App is the inverse of what we already shipped as Ask AI Apps: Ask AI Apps let the AI call out to Slack/Jira/Gmail from the web composer. The Slack App lets you call in to Ask AI from Slack. Both work together; you can install both and they don't overlap.

What you can do today

/testrelic slash commands

/testrelic <prompt> runs the prompt through the same Ask AI runtime as the web composer — same tool calls, same context, same artifact types. Responses thread under your message with charts and deep links:

Channel: #qa-leads

/testrelic which tests broke after yesterday's deploy?

Channel: #checkout-team

/testrelic show me the flakiest tests in the checkout suite over the last 7 days

Threaded follow-ups continue the same Ask AI conversation, so context like @repo or @test_run set on the first prompt carries through. You can chain prompts the way you'd chain DM replies.

Scheduled QA digests

Any Ask AI prompt can be scheduled as a recurring digest to a Slack channel. We use these internally:

• Weekly flaky digest to #qa-leads every Monday 9am — three stat tiles (pass rate, flaky %, MTTR) plus the top five offenders with retry counts.
• Nightly regression alert to #oncall after the prod E2E run — only posts if something failed.
• Monthly compliance evidence to a private channel — a generated PDF report uploaded as a Slack file for audit retention.

Create one by running the prompt once, then clicking Share → Schedule to Slack on the artifact. Or skip the web app entirely:

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

Manage all schedules at Settings → Integrations → Slack → Schedules.

Share-back from the web app

Every artifact in the Ask AI panel has a Share → Slack action. Pick a channel, add a message, and the artifact posts as a rich Slack card with metric snapshots and a deep link. Presentations and reports upload as Slack files so they stay searchable.

The artifact types that round-trip cleanly today:

Artifact	Slack representation
dashboard	Card with 3 stat tiles + sparkline + deep link
report	Markdown summary + uploaded PDF
test_plan	Numbered list + uploaded markdown file
presentation	Card with cover thumbnail + uploaded slide deck
data_table	Slack table block (up to 50 rows)
chart	Inline image preview + deep link

Failure alerts on quality gates

Connect a monitoring quality gate to a Slack channel and the gate posts the moment it fails — with the failing test case, the threshold that was crossed, and an Open in TestRelic button. Reply in the thread with /testrelic was this a flake or a real regression? and the AI inspects retry patterns and CI metadata before answering. We use this to triage on-call without leaving Slack.

Sample use cases

A few patterns from our design partners and our own team:

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.

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 deck uploads 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.

Compliance evidence

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

Uploaded as a PDF, linked back to the underlying TestRelic runs.

Plan and privacy notes

The Slack App talks to Ask AI, which is part of the Growth plan (Plans & Billing). On Starter orgs, /testrelic responds with an upgrade prompt.

A few privacy details worth calling out:

• Conversations are unified. Slack-originated conversations show up in the Ask AI Chat Sidebar in the web app, tagged with a Slack badge. Memory is scoped to your TestRelic user, so triggering /testrelic from Slack and continuing from the web app under the same account gives you continuous memory.
• Channel messages are not ingested. The app only acts on prompts directly addressed to it (slash commands, scheduled digests, share-back). It does not read general channel traffic.
• Same training policy as the rest of Ask AI. Prompts and responses are stored in your governed conversation history and are never used to train shared models.

Full scope list, install steps, and troubleshooting live on the Slack integration page.

Installing

The fastest path:

1. Open Settings → Integrations in the TestRelic web app.
2. Click Connect on the Slack card.
3. Pick the workspace and channel; the app installs in well under a minute.

Or install directly from the Slack App Directory. The first slash command from any user prompts them to link their Slack identity to a TestRelic account — one-time, per user.

What's next

A few things on the near-term roadmap based on design-partner feedback:

• @slack-thread context — attach a Slack thread as context to an Ask AI prompt, so the AI can pick up the conversation where the channel left off.
• Per-channel default scopes — pin @repo or @environment to a channel so /testrelic prompts there inherit it automatically.
• Workflow Builder steps — drop TestRelic actions into Slack Workflows for no-code triage flows.
• Bidirectional Jira — file a Jira ticket from a Slack alert thread with one click, pre-filled with the failure context.

If any of these are blocking for your team, ping us in our public Slack — the design partners we work with shape what ships next.

Related documentation

• Slack Integration — full reference, scopes, troubleshooting
• Ask AI — runtime, artifacts, memory, Ask AI Apps
• AI Insights & Artifacts — what each artifact type looks like
• Plans & Billing — Growth plan limits and AI token quotas
• Jira Integration — for /testrelic open a ticket follow-ups

FAQ: Which plan unlocks the Slack App?

The Slack App talks to Ask AI, which is part of the Growth plan. The integration itself can be installed on any plan, but /testrelic prompts on Starter orgs return an upgrade message.

FAQ: Does the app read general Slack channel traffic?

No. The app only acts on prompts directly addressed to it (slash commands, scheduled digests, share-back). It does not ingest general channel messages.

FAQ: Can I run /testrelic in a DM?

Yes. DMs work like channels — same slash command, same threading behavior. DM history is private to the inviting user and is not visible to other org members in the Ask AI Chat Sidebar.

FAQ: Where do I manage scheduled digests?

Settings → Integrations → Slack → Schedules in the web app. Pause, edit cadence, or change the destination channel inline.