Ask AI is TestRelic’s primary full-page conversational interface for turning natural language into answers about your organization’s tests, runs, and quality signals—and, when appropriate, into structured artifacts you can share or iterate on. The authoritative specification lives in the Ask AI documentation; this article expands that material with additional cross-links for teams evaluating Ask AI against IDE-only tooling such as the TestRelic MCP server.

Coding assistants are only as good as the context they see. Pasting stack traces into chat scales poorly; re-fetching structured run history from your org is better. The TestRelic MCP server implements the Model Context Protocol so compatible hosts—Cursor, Claude Desktop, VS Code MCP clients, and others—can call tools that read your TestRelic cloud projects, runs, coverage signals, and related data. The MCP overview positions MCP alongside the SDK reporters: reporters write run data from CI and laptops; MCP reads and acts on that data inside the IDE loop.

If you run Playwright in CI, you already have pass/fail signals. Testing observability means capturing the execution story around each failure: which URLs you touched, how the SPA navigated, what the network layer did, and which build or branch produced the run. The @testrelic/playwright-analytics reporter is designed for that workflow—it runs locally, writes structured JSON and HTML, and can feed the TestRelic cloud platform when you add an API key. This guide consolidates the official docs into one narrative for teams standardizing on Playwright.

Welcome to the official TestRelic documentation. Whether you ship browser suites with Playwright, mobile automation with Appium and WebdriverIO, or Maestro flows, the same idea applies: capture structured execution signals locally, optionally sync them to the cloud, and use dashboards, AI, and integrations to shorten mean time to understand a failure.

This hub page orients new readers: what TestRelic is, which packages to install, how the cloud fits in, and where to read next—including longer blog articles that tie multiple doc sections together for SEO-friendly learning paths.