ReleaseQA for Playwright

Know which Playwright runs are actually green.

Get a release-readiness score, flake detection, and commit-linked regressions for your Playwright suite — without leaving @playwright/test.

Install

Two copy-pastes. One quality score.

1 · install
$ npm i -D @releaseqa/reporter-playwright
2 · config
// playwright.config.ts
import { defineConfig } from "@playwright/test";

export default defineConfig({
  reporter: [
    ["list"],
    ["@releaseqa/reporter-playwright", {
      apiKey: process.env.RELEASEQA_API_KEY,
      project: "web",
    }],
  ],
});

Set RELEASEQA_API_KEY in your CI secrets and push. First run appears in under 2 minutes.

Built for Playwright

Four signals your CI can’t give you.

Retry-aware flake scoring

Respects your retries config. A test that passes only on retry is flagged flaky — not quietly marked green.

Trace & screenshot attachments

Playwright's built-in trace.zip and failure screenshots ride along with each run, so regressions open with full context.

Project and shard aware

One score per project. Sharded runs merge cleanly; parallel workers don't inflate duration numbers.

Fixture-level ownership

CODEOWNERS maps to test files, so every failure names the team that owns it.

Frequently asked

Playwright-specific questions.

  • Does it work with component tests (@playwright/experimental-ct)?
    Yes. Any test emitting via the @playwright/test runner flows through the reporter, including component tests.
  • What about UI-mode and headed debugging?
    The reporter only emits when a CI env var is set (or when you pass `ci: true`). Local `pw test --ui` runs stay out of your org.
  • Does it slow down my suite?
    The reporter batches over HTTP keep-alive. Measured overhead on a 500-test suite: <2 seconds of total wall time.

Score your Playwright suite in 5 minutes.

Free forever tier · No credit card · Cancel anytime.

Start free →Read the docs