Query your app's memory in plain English.
testrelic "why did checkout fail?"Every test run becomes shared context for Cursor, Claude Code, Copilot, and Codex — over MCP. So your whole team ships at senior-IC speed, not just the engineer who's been here longest.
Today
This Week
Older
Ask anything about your tests
Grounded in 214 specs and 30 indexed runs from shop-e2e.
LevichHow Ask AI works
Three steps from question to artifact
No dashboards to configure, no filters to set.
You ask in natural language
Type a question or request the way you'd say it to a colleague. No special syntax, no query language.
No query language. No filters to set.
AI reads your test data
Your prompt is mapped to live test runs, failure logs, coverage metrics and historical trends — every number sourced, none invented.
Reading your live runs — every number is sourced, none invented.
Prompts and outputs are never used to train shared models.
You get a shareable artifact
A dashboard, plan, report or deck, rendered from your actual data — and shareable straight back into Slack or Teams.
Flake rate
13.3%+9.1
MTTR
4.2h−38%
Pass rate
96.1%−1.4
Where your team works
The same grounded answers, in Slack and Teams
No context-switching — ask from the channel you're already in.
Slash commands in Slack
Type /testrelic anywhere your team works. Answers thread under your message with charts and deep links, scheduled QA digests pin to any channel, and any Ask AI artifact shares back in one click.
acme
Channels
# eng-quality
# releases
# incidents
Apps
TestRelic
# eng-quality
dana10:42
/testrelic why did checkout fail?
TestRelicApp10:42
checkout.spec.ts · 4/30 failing
[data-test=pay-now] was renamed in v2.4.1 — all failures are post-deploy, not timing.
Weekly QA digest pinned · Mondays 9:00
Adaptive Cards & Tabs in Teams
@mention the TestRelic bot for an instant Adaptive Card with drill-down buttons, pin a live QA dashboard as a channel Tab, and get regression and flaky-spike alerts in the activity feed.
Add to TeamsQuality › General
Sarah9:14 AM
@TestRelic flake rate this sprint?
TestRelic · Quality digest
Flake rate
13.3% ▲ +9.1
MTTR
4.2h ▼ −38%
Pass rate
96.1%
Regression and flaky-spike alerts in the activity feed.
What you can generate
Every artifact is rendered live from your test data
Not templates — your actual runs.
Dashboards, reports and decks
Ask for a test-health dashboard, a weekly QA summary, or a sprint-review deck. Pass rates, MTTR, flaky trends, P0 escapes, coverage tables — populated from your real runs and formatted to send.
Pass rate
96.1%−1.4
P0 escapes
0
Flake rate
13.3%+9.1
MTTR
4.2h−38%
Failures by week
Top offenders
Also renders as a live dashboard or a stakeholder deck — same data, formatted for the audience.
Test plans and path maps
Describe a feature and get a structured regression plan with prioritized cases, coverage gaps and edge cases. Describe a journey and get a visual map of the critical paths through it.
Cases
14
Coverage gaps
2
Prioritized cases
Test path map
6 edge cases suggested from the runs behind this flow.
Plain English queries
Ask anything — which tests broke after last deploy, what's the flakiest suite this week. No SQL, no filters, just answers grounded in your runs.
All three trace to [data-test=pay-now], renamed in v2.4.1.
No SQL, no filters — grounded in 30 runs.
Start asking questions, get real answers.
Ask AI is included in the Growth plan. Start your 14-day free trial — no credit card required. Prompts and outputs are never used to train shared models; enterprise deployments support bring-your-own LLM (BYOL) for full data isolation.