Analyze and improve your tests with Rocky AI

Run your full test suite on your own infrastructure or from Checkly's 20+ global locations with a single command. Rocky AI analyzes every failure, groups errors, gives you fast root cause analysis, and helps you fix the problem.

npm install --save-dev @checkly/playwright-reporter
bash — playwright test
$ npx playwright test
Running 8 tests using 4 workers
✓ auth › login succeeds [310ms]
✓ auth › logout clears session [290ms]
✓ nav › homepage loads [220ms]
✗ checkout › complete payment [3.2s]
✓ nav › pricing page renders [180ms]
✓ docs › search returns results [460ms]
✓ api › POST /orders returns 201 [190ms]
✓ api › GET /products returns list [210ms]
7 passed, 1 failed
Uploading session to Checkly...
✓ Session created
→ https://app.checklyhq.com/test-sessions/rpt_8xkp2

The Problem

Agents write tests faster than you can make sense of them

When agents generate hundreds of tests, you need a cloud that thinks as fast as they do. Checkly analyzes every result with Rocky AI, surfaces what actually matters, spots flaky tests before they waste your time, and hands back clear answers.

Results end up scattered

CI logs, local traces, and HTML reports with no shared home for team review.

Patterns stay invisible

Without history across builds, recurring failures and flaky tests go unnoticed.

Debugging is still manual

Making sense of failures still requires opening files locally and piecing context together.

What You Get

More than a place to store results.

Once test results are in Checkly, Rocky AI can analyze them, your team can track what keeps failing over time, and developers get a richer UI to pinpoint what went wrong.

AI Analysis

Rocky AI analyzes every failure.

Root Cause

The backend service encountered an internal server error (500) on the /users/me endpoint and a DNS resolution failure (ENOTFOUND) when connecting to the authentication provider, preventing the application from loading user-specific UI components.

Evidence2
  • The test timed out waiting for the 'select the location' button, which typically indicates the page failed to render completely or the user session was not correctly established.

    error
  • OpenTelemetry spans show a 500 Internal Server Error for the 'api.checklyhq.com/users/me' endpoint and a 'getaddrinfo ENOTFOUND' error for 'checkly.eu.auth0.com', indicating critical infrastructure and dependency failures.

    otel spans

When a test fails, Rocky AI reads the traces, network requests, and console logs automatically captured by the reporter and returns a root-cause analysis — no manual digging required.

Test History

Track what keeps failing over time.

Test Sessions

Search by project, environment, branch, user, commit/
Showing 1-20 test sessions
Project
Environment
Branch
Commit
Duration
User
Run Date
Atlas Dashboard
All passed
production
main
4b5f93d
4 min 45 s
GitHub Actions
5 minutes ago
Atlas Visual Tests
All passed
production
main
4b5f93d
10.55 s
GitHub Actions
6 minutes ago
Nova Status Page
2 failed
staging
fix/status-widget
2e51b01
3 min 22 s
JL
Jordan Lee
6 minutes ago
Nova Status Page
2 failed
staging
fix/status-widget
2e51b01
3 min 7 s
JL
Jordan Lee
12 minutes ago
Atlas Dashboard
All passed
production
main
ecf99f1
4 min 22 s
GitHub Actions
21 minutes ago

Every run is stored as a shared session in Checkly. Review failures across builds, spot recurring issues and flaky tests, and understand trends — something a local HTML report can't give you.

Trace Viewer

Replay failures step by step.

Replay failures step by step.

Playwright traces captured during the run are stored alongside results. Walk through each step with screenshots, network activity, and timing — without needing to reproduce the failure locally.

Network & Console

Every artifact you need to debug, in one place.

Search by test title/
2 failed, 20 passed, 2 skipped
54.73 s
desktop-light
__checks__/e2e/homepage.spec.ts
__checks__/e2e/checkout-flow.spec.ts
Checkout Flow
should navigate to checkout from homepage
public
4.1 s
should complete purchase with valid card details
public
39.99 s
mobile-light
__checks__/e2e/homepage.spec.ts
__checks__/e2e/checkout-flow.spec.ts
Checkout Flow
should navigate to checkout from homepage
public
7.18 s
should complete purchase with valid card det...
public
43 s
Errors

Error: Timed out 10000ms waiting for expect(locator).toBeVisible()

Locator: getByText('Order confirmed', { exact: true })

Expected: visible

Received: <element(s) not found>

Call log:

– expect.toBeVisible with timeout 10000ms

– waiting for getByText('Order confirmed', { exact: true })

64| */
65| async waitForConfirmation (): Promise<void> {
>66| await expect(this.confirmBanner).toBeVisible({ timeout: 10000 })
67| }
68|
69| /**

at CheckoutPom.waitForConfirmation (/tmp/playwright-UFGgmg/user/__checks__/poms/CheckoutPom.ts:66:44)

at /tmp/playwright-UFGgmg/user/__checks__/e2e/checkout-flow.spec.ts:52:27

Steps
Network
Type to filter
Show errors only
URL
Status
Method
Type
Duration
https://atlas-app-preview.vercel.app/cart/checkout200GETdocument140 ms
https://atlas-app-preview.vercel.app/_next/static/chunks/checkout.js200GETscript36 ms

Screenshots, videos, network requests, console errors — every piece of evidence from a test run is captured and surfaced automatically. No more hunting through CI logs or re-running locally just to see what went wrong.

Run from 20+ global locations

Use npx checkly test in your CI pipeline to run from Checkly's global infrastructure. Catch regional failures and latency spikes before they hit production.

Automatic secret scrubbing

API keys, tokens, and passwords are redacted before upload. No extra config. Available on all plans, including free.

CPU & memory graphs

Track system resource usage during each test run. Spot whether flaky or failing tests correlate with resource pressure.

Git metadata, automatically

Branch, commit hash, and author are attached to every session automatically from GitHub Actions, GitLab CI, CircleCI, and local repos.

The Bigger Picture

From CI to production, in one platform.

Checkly Testing closes the loop between CI and production. Run from your own infrastructure or Checkly's global locations, analyze every failure with Rocky AI, and promote the checks that matter into always-on monitors — without switching platforms.

01
npx checkly test

In your CI/CD pipeline

Run & report

Run your Playwright tests on your own infrastructure with the reporter, or use npx checkly test to run from Checkly's 20+ global locations. Traces, videos, logs, and results land in Checkly automatically.

02
Checkly Dashboard

Cloud-hosted sessions

Analyze & track

Rocky AI analyzes each failure. History accumulates across runs. Teams get a shared, persistent home for test results — with richer debugging context than a local report.

03
npx checkly deploy

Production monitoring

Monitor in production

Take the tests that matter and deploy them as always-on monitors from 20+ global locations. The only reporter that offers this path.

Setup

Two minutes to install.

No cloud infrastructure to provision. No storage accounts to configure. Your existing npx playwright test workflow stays exactly the same — or run directly on Checkly's global infrastructure with npx checkly test.

01

Install

npm install --save-dev @checkly/playwright-reporter
02

Configure

playwright.config.ts
1import { createChecklyReporter } from '@checkly/playwright-reporter'
2 
3export default {
4 reporter: [
5 ['list'],
6 createChecklyReporter(),
7 ],
8}
03

Set credentials

.env
1CHECKLY_API_KEY=cu_...
2CHECKLY_ACCOUNT_ID=b2f...
04

Run tests

npx playwright test

Your tests deserve a
production-grade home.

Connect your Playwright tests, get AI-powered failure analysis, and promote the checks that matter to always-on production monitors. Free to start, no credit card required.