AI Insights & Artifacts

TestRelic's AI produces two categories of structured output: session insights (automatically generated analysis of individual test sessions) and artifacts (structured outputs generated through AI chat interactions).

Session AI Insights

Session insights appear in the Insights tab of the Session Workspace. They are automatically generated when you open a session on the Growth plan.

Growth plan required

AI Insights require the Growth plan. See Plans & Billing.

What insights include

Insight type	Description
Defects	AI-identified defects in the test session — categorized by severity, likely cause, and whether the issue is a test problem or an application bug
User impact	Assessment of the user-visible impact if the failing behavior reached production
Jira linkage	Matches the detected defect against open Jira issues (when the Jira integration is connected)
MTTR panel	Mean Time to Resolution estimate based on similar historical failures in your repository

Insights panel components

The InsightsPanel in the Session Workspace renders:

1. A list of detected defects with severity labels and expandable detail sections.
2. User impact summary — a brief description of what end users would experience.
3. Linked Jira issues — existing tickets that match the failure pattern.
4. MTTR estimate with a confidence indicator.

AI Artifacts

Artifacts are structured outputs produced by the AI during a conversation in Ask AI or the AI Assistant. Each artifact appears in a dedicated rendering panel alongside the chat response.

Artifact types

Dashboard

A rendered analytics dashboard with multiple metrics panels and charts. Useful for generating executive-facing quality summaries.

Typical trigger: "Create a dashboard showing pass rates, flaky tests, and failure trends for this week."

Report

A formatted test quality report with sections, tables, and analysis. Exported as readable markdown.

Typical trigger: "Generate a weekly test quality report for the payments team."

Test Plan

A structured test plan document with test scenarios, steps, expected results, and coverage notes.

Typical trigger: "Write a test plan for the user registration flow covering happy path, validation errors, and duplicate email scenarios."

Code

A code snippet rendered with syntax highlighting. Commonly used for new test code, reporter configurations, or CI workflow snippets.

Typical trigger: "Write a Playwright test for the login flow."

Data Table

A tabular breakdown of test data — useful for comparing test metrics across repositories, branches, or time periods.

Typical trigger: "Show me a table of failure rates by repository for the last 30 days."

Chart

An inline data visualization (bar, line, or pie chart) rendered in the artifact panel.

Typical trigger: "Plot pass rate trends for the last 4 weeks."

Navigation Paths

A visual map of test navigation paths, similar to the Test Navigation view, but generated as part of an AI response.

Typical trigger: "Show me the navigation coverage gaps in the checkout flow tests."

Artifact presentation

Artifacts render in the right-hand panel of the Ask AI page, separate from the chat messages. Multiple artifacts from the same conversation are stacked and navigable. Each artifact includes:

• A title (set by the AI based on the request)
• The artifact type badge
• The rendered content
• A creation timestamp

Sharing artifacts via links

Any artifact you generate in the Ask AI panel — dashboard, report, test_plan, presentation, data_table, or chart — can be shared with a link, similar to sharing a file in Google Drive.

Generating a link

From the artifact toolbar, choose the share action and pick a visibility. TestRelic produces a link you can copy and send. The link opens a read-only rendering of the artifact, including the filters it was generated with, so the recipient sees the same view you did.

Public vs. private links

Visibility	Who can open it
Public	Anyone with the link — no TestRelic account needed. The artifact renders as a read-only view, with its filters applied.
Private	Only signed-in members of your organization. Opening the link requires org sign-in.

note

Public links render a read-only view to anyone who has the URL. Use private links for artifacts that should stay within your organization.

The artifact library

Shared artifacts are collected in an artifact library, where they are listed for later reference. Library entries can also be shared — so you can re-share an artifact, or change how it is shared, without regenerating it.

Feedback on AI outputs

Every AI message and artifact can be rated with thumbs up or thumbs down feedback. This feedback is stored and used to improve model quality over time.