From your first run to the last flaky test.
Guides and references for the TestRelic CLI, Studio, SDKs, MCP server and Cloud Platform: the agent in your terminal, the app on your desktop, and the platform every run lands in.
testrelic init in your project.curl -fsSL https://testrelic.ai/install.sh | sh$ testrelic init
✓ Detected Playwright (TypeScript) · playwright.config.ts
✓ Wired @testrelic/playwright-analytics reporter
▶ Running suite once… 42 passed · 1 flaky (retried)
✓ Analytics report written to .testrelic/report
✻ Opening TestRelic Studio…
Pick your way in.
Most teams start in the terminal. You can also add a reporter to a suite you already have, or give your AI coding agent your test data.
- 1Install the CLI with one command.
- 2Run
testrelic init. It wires the reporter and runs your suite once. - 3Studio opens. Ask why a test failed.
- 1Pick your framework: Playwright, Appium, Maestro or pytest.
- 2Install its TestRelic SDK reporter.
- 3Upload your runs to the Cloud Platform.
- 1Use the hosted server at
mcp.testrelic.ai, or run it withnpx. - 2Create a token for your agent.
- 3Ask about failing runs, right from your editor.
The CLI needs the Growth plan or above and Studio needs Pro or above; an active 14-day trial covers both. Plans & billing
Explore by product.
-p for scripts and CI.Recently shipped.
- CLICLI and Studio fixes: uploads after login, local models, and docking the chat
- CLIStudio tests mobile apps on a live Android device
- CLICLI fixes: keys typed under prompts, the first run of init, and upload retries
- Cloud PlatformAsk AI: code in Remote sessions opens in the Artifact pane, with what changed
- MCP ServerMCP tools count a run's failures the way the run does
- Cloud PlatformFixes: accessible sign-in pages, large uploads, and device sign-in at the token limit
- CLIStudio's bash terminals and Live Browser DevTools work again
Start in your terminal.
Install the CLI, run testrelic init, and your first run opens in Studio.
curl -fsSL https://testrelic.ai/install.sh | sh