Test failures break trust. Fix them faster.
Developer first. Always.
Built for AI testing teams. No bloat, no BS — just the tools you need to ship quality software.
One-Line Setup
Drop in the SDK. No agents to install. No infrastructure to manage. One line of config and you're capturing structured test data.
Everything's connected
Other tools exist. But test logs, AI triage, MTTR tracking, and user impact — all connected by the same intelligence layer? That's our thing.
Unified Test Logs
Every test result, CI trace, and execution log flows into one unified timeline. No more jumping between 5 different tools.
checkout.spec.ts — 3 passed, 1 failed
CI Build #2847 completed
Cross-browser run — Chrome, Firefox, Safari
Checkout conversion dropped 8%
BUG-1234 auto-created from test failure
TestRelic AI uses your test data, deployment history, and user analytics to go beyond “what failed” and tell you “why it matters.”
Correlates failures to user impact
TestRelic AI connects test failures to real user journeys. When checkout tests break, you instantly see how many users are affected, what revenue is at risk, and which deployment caused it.
Auto-creates tickets with full context
Every auto-triaged issue becomes a ticket with stack traces, screenshots, related test history, and user impact data. Your engineers get everything they need to fix it — no back-and-forth.
Predicts flaky tests before they break
AI analyzes historical patterns — timing variance, environment sensitivity, data dependencies — to flag tests likely to become flaky. Fix them before they erode trust in your suite.
Get started in minutes
One command. One config line. That's it. No complex setup, no performance hits.
I want to set up the @testrelic/playwright-analytics SDK in my existing Playwright project. Please help me do the following:
1. Install the package:
npm install @testrelic/playwright-analytics
2. Update playwright.config.ts to use the TestRelic reporter via defineConfig:
import { defineConfig } from '@testrelic/playwright-analytics';
export default defineConfig({
testDir: './tests',
// video, screenshot, trace & TestRelic reporter configured automatically
});
3. Update test files to use the TestRelic fixture:
- E2E tests: import { test, expect } from '@testrelic/playwright-analytics/fixture';
- API tests: import { testRelicApiFixture } from '@testrelic/playwright-analytics/api-fixture';
- Unified (browser + API): import { test, expect } from '@testrelic/playwright-analytics/fixture';
4. (Optional) Connect to the TestRelic cloud platform:
- Get an API key from platform.testrelic.ai → Settings → API Keys
- Create .testrelic/testrelic-config.json:
{
"cloud": {
"apiKey": "$TESTRELIC_API_KEY",
"endpoint": "https://platform.testrelic.ai/api/v1",
"upload": "both"
},
"testrelic-repo": { "name": "my-project" }
}
- Set env variable: export TESTRELIC_API_KEY=your_api_key_here
The SDK captures: navigation timelines, API calls, network stats, test results, failure diagnostics, CI metadata (GitHub Actions / GitLab CI / Jenkins / CircleCI), screenshots, videos, action steps, and console logs. It generates a JSON + HTML report at ./test-results/analytics-timeline.
Please walk me through each step and adapt the configuration to match my project structure.AI-driven testing. Ship with confidence.
Get started with the only engineering testing platform that connects test data, AI triage, and user impact in one place.