Your AI knows code. We give it memory of your app.
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.
Levich
Your AI knows code. We give it memory of your app.
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.
Levichusers affected
via AmplitudeTrusted integrations
WHY A MEMORY LAYER
Your AI is only as smart as what it knows about your app.
Vanilla LLMs know syntax. They don't know your codebase's flaky flows, last sprint's selector changes, or which user paths break under load. TestRelic captures all of that from your tests and shares it with every engineer's AI agent — over MCP.
Cursor, Claude Code, Copilot, and Codex stop guessing about your app — they read shared application context derived from real test runs.
The flows, gotchas, and 'you have to know X before touching Y' that lived in one engineer's head — now in every teammate's AI session.
One SDK per framework, one MCP block in your agent config. Test runs start filling shared memory immediately. No infrastructure, no overhead.
Sources: DORA 2024 · DORA 2024 PDF
- AI root cause surfaced in under 5s
- No manual log triage required
- Works across Playwright, Appium, Maestro
WHO READS THE MEMORY
One memory layer. Every role on the team.
QA fills the memory with what they learn debugging. Engineering Leads watch tribal-knowledge bottlenecks disappear. Platform/DevX teams pipe it into every AI coding agent on the org.
Your test runs become the team's application memory.
- Every failed run, broken selector, and flaky pattern gets captured into shared context
- What you learn debugging at 3am is what every teammate's AI agent reads tomorrow morning
- Nested session trees with video, steps, console, and network — surface for humans, substrate for AI
Duration
4m 12s
Tests
7
Frameworks
2
Pass Rate
71%
Failures
2
INSIDE THE MEMORY LAYER
Application Memory.
Shared Context. Team Intelligence.
Three pillars on one substrate: every Playwright, Appium, and Maestro test run becomes memory of your app — surfaced to humans through dashboards, to AI agents through MCP.
WHAT TESTRELIC REMEMBERS ABOUT YOUR APP
Test-run history, flaky patterns, broken selectors, slow flows, deploy correlations, and user-impact mapping — all kept as durable context for every engineer's AI agent. Not generic LLM knowledge. Your app, specifically.
Correlates failures to user impact
TestRelic AI connects test failures across web and mobile to real user journeys. When checkout tests break on Playwright or the login flow fails on Android via Appium, 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 Jira ticket with stack traces, screenshots, device logs, related test history, and user impact data. Whether the failure is from Playwright, Appium, or Maestro — engineers get everything they need to fix it.
Predicts flaky tests before they break
AI analyzes historical patterns across all frameworks — timing variance, environment sensitivity, device-specific instability, data dependencies — to flag tests likely to become flaky. Fix them before they erode trust in your suite.
SDK INTEGRATIONS
Set up in seconds with your AI agent
Copy the prompt for your framework — JavaScript or Python — and paste it into Cursor, Claude, or Copilot. Your AI agent installs the SDK, wires up the reporter, and connects your local test runs to TestRelic automatically.
1Set up TestRelic Playwright analytics in my project (local run).23Step 1 — Install the SDK:4 npm install @testrelic/playwright-analytics56Step 2 — Add the reporter to playwright.config.ts:7 reporter: [8 ['list'],9 ['@testrelic/playwright-analytics', {10 includeNetworkStats: true,11 includeCodeSnippets: true,12 }],13 ],1415Step 3 — Import the TestRelic test fixture in your specs:16 import { test, expect } from '@testrelic/playwright-analytics/fixture';1718Step 4 — Add your credentials to a local .env file:19 TESTRELIC_API_KEY=<paste your key here>20 TESTRELIC_REPO_ID=<paste your repo id here>2122Step 5 — Run your tests locally:23 npx playwright test2425Results, AI triage, and session replays appear automatically26on platform.testrelic.ai.2728Get your API key → platform.testrelic.ai/signup
HOW THE MEMORY LAYER WORKS
Capture · Remember · Share
Inject into every AI agent.
CAPTURE
Install one SDK — Playwright, Appium, or Maestro. Your existing tests now feed the memory layer with every run.
REMEMBER
TestRelic stores what your app actually does: flaky flows, broken selectors, failure patterns, user-impact mapping.
SHARE
One org-scoped memory layer — not per-IDE local memory. Every teammate's AI agent reads from the same context.
INJECT
Connect Cursor, Claude Code, Copilot, Codex, or any MCP client. Your app's memory becomes a tool every agent can read on every turn.
CAPTURE
Install one SDK — Playwright, Appium, or Maestro. Your existing tests now feed the memory layer with every run.
REMEMBER
TestRelic stores what your app actually does: flaky flows, broken selectors, failure patterns, user-impact mapping.
SHARE
One org-scoped memory layer — not per-IDE local memory. Every teammate's AI agent reads from the same context.
INJECT
Connect Cursor, Claude Code, Copilot, Codex, or any MCP client. Your app's memory becomes a tool every agent can read on every turn.
INTEGRATIONS
Stay in your stack.
We'll meet you there.
JavaScript and Python SDKs for Playwright, Appium, Maestro, pytest, and DeepEval. Plus integrations with the tools your team already uses.
Integrations
COMMUNITY
The future of test quality
depends on you.
Join the community building better test observability workflows.
NPM
@testrelic
INSTALL IN SECONDS
Install the TestRelic SDK packages directly from npm. Zero lock-in, works with your existing test setup.
PYPI
testrelic-*
INSTALL IN SECONDS
Install the TestRelic Python SDKs from PyPI — pytest plugins for Playwright analytics and DeepEval evals.
GITHUB
testrelic-ai
AGPL-3.0 LICENSED
Explore the source, file issues, and contribute. SDKs, the MCP server, and more — all open source.
DOCUMENTATION
docs.testrelic.ai
3 FRAMEWORKS COVERED
Quickstart guides, API references, and framework-specific setup tutorials.
CLI
testrelic
ASK AI IN YOUR TERMINAL
The TestRelic Ask AI agent in your terminal — Claude Code-style, with a full MCP host. Install in one line.
ENTERPRISE
Built for teams that can't
afford to get it wrong.
Security and compliance aren't checkboxes — they're built into how we run TestRelic AI.
Get tailored supportSOC 2 TYPE II
Enterprise-grade compliance and security controls for regulated industries.
GDPR COMPLIANT
Full data privacy compliance for global teams with regional data residency.
END-TO-END ENCRYPTION
All data encrypted at rest and in transit. We never use your data to train models.
ON-PREMISE OPTION
Deploy on your own infrastructure — AWS, Azure, or GCP with hands-on support.
99.9% UPTIME SLA
Enterprise-level guarantees for mission-critical testing workflows.
RBAC & DATA MASKING
Custom permissions control, project-level data separation, and trace masking.
Wire your AI agents into your app's memory.
TestRelic is the test-derived memory layer your team's AI coding agents are missing. Built on Playwright, Appium, and Maestro. Connects to Cursor, Claude Code, Copilot, and Codex over MCP.
Industry Pulse