TestRelicCloud Platform Overview
An overview of the TestRelic cloud platform — the unified hub for test analytics, AI-powered insights, monitoring, and integrations across Playwright and Appium test suites.
Purpose
The TestRelic cloud platform is the web application that centralizes test analytics, AI-driven insights, monitoring dashboards, and third-party integrations — for Playwright browser tests and Appium mobile tests.
Prerequisites
- An account at testrelic.ai (sign up or accept an invite).
- Test data from the SDK reporters when you want live runs in the platform (optional for exploring empty orgs).
The SDK reporters (@testrelic/playwright-analytics and @testrelic/appium-analytics) run locally alongside your tests and generate structured output. The cloud platform is where that data is stored, visualized, and acted on.
Concept: data path from tests to the platform
Platform pillars
| Pillar | What it provides |
|---|---|
| Test Runs & Sessions | Org-wide test run dashboard with CI environment context, filterable run lists, and deep session inspection |
| Repositories | Connect your test repositories, view health metrics, pass rates, and manage framework setup |
| LLM Evaluations | Ingest DeepEval LLM-evaluation runs, browse them through the shared run UI, and track Eval Stability over time |
| AI & Intelligence | Ask AI chat, floating AI assistant, session-level AI insights, and structured artifact generation |
| Test Navigation | Pathfinder and tree-view maps of your test suite's navigation patterns and coverage |
| Monitoring | Smoke, regression, and nightly observatory dashboards for automated quality gates |
| Integrations | Native connections to GitHub Actions, Jira, Grafana Loki, Amplitude, TestMu AI, and BrowserStack |
| Administration | User management, API keys, billing, audit logs, and usage analytics |
Where SDK-backed data surfaces
The product is organized around runs, repos, AI, monitoring, and admin once data reaches the cloud.
Key concepts
Organizations
Every TestRelic account belongs to an organization. All repositories, test runs, integrations, and AI conversations belong to the organization and are shared across team members.
Repositories
A repository in TestRelic maps to one test project (typically one Git repository). Repositories are the top-level grouping for test runs, navigation graphs, and health metrics.
Test Runs and Sessions
A test run is a single execution of your test suite — one invocation of npx playwright test or npx wdio run wdio.conf.ts. Each run contains one or more sessions (individual test cases). The platform captures:
- Pass/fail/flaky status per session
- Step-by-step execution timeline
- Network requests and console output
- Device logs and Appium command traces (mobile runs)
- Video recordings (when available)
- CI environment context (GitHub Actions, GitLab CI, Jenkins, CircleCI)
Feature Flags
Some platform features (Monitoring, Integrations) are controlled by PostHog feature flags at the organizational level. Contact your administrator if a section is not visible in your navigation.
Accessing the platform
Navigate to testrelic.ai and sign in with your email and password. New users are guided through an onboarding wizard that sets up your profile and first repository connection.
Troubleshooting
| Symptom | What to try |
|---|---|
| No runs appear after CI | Confirm the reporter uploads or sync path for your setup, and that the correct organization and repository are selected in the UI. |
| A navigation item is missing | Feature flags may hide Monitoring or Integrations for the org — ask an admin. |
What's next?
- Authentication — Sign up, log in, manage roles, and accept invitations
- Onboarding — Configure your profile and framework settings
- Plans & Billing — Understand Starter vs Growth features and limits
- Dashboard & Test Runs — Explore your test run history
Connect your first repo
The fastest way to get value from the platform is to connect a repository using an API key.
- Playwright → Get Started with Playwright
- Appium / WDIO → Get Started with Appium