@brittlehq/playwright-reporter
v0.2.1
Published
Brittle reporter for Playwright — streams test results to the Brittle Hub in real time
Maintainers
Readme
@brittlehq/playwright-reporter
Stream Playwright test results to Brittle — failure triage, AI-grouped errors, flake history, command + network logs — without changing how your tests run.
Install
pnpm add -D @brittlehq/playwright-reporter
# or: npm i -D @brittlehq/playwright-reporter
# or: yarn add -D @brittlehq/playwright-reporterConfigure
Add the reporter to playwright.config.ts:
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['list'],
[
'@brittlehq/playwright-reporter',
{
url: process.env.BRITTLE_URL,
token: process.env.BRITTLE_TOKEN,
},
],
],
});Set the env vars in your shell or CI:
export BRITTLE_URL=https://brittle.dev # or your self-hosted hub
export BRITTLE_TOKEN=brt_svc_xxxxxxxxxxxxxxxx # mint at Project → Settings → TokensIn CI, set BRITTLE_TOKEN as a secret and BRITTLE_URL as an environment
variable in the workflow.
All options
{
url?: string; // defaults to process.env.BRITTLE_URL
token?: string; // defaults to process.env.BRITTLE_TOKEN
runName?: string; // groups parallel workers into one Run row
target?: string; // 'prod' / 'staging' / app version label
tags?: string[]; // e.g. ['nightly', 'smoke']
// Explicit git overrides — only set when CI env is more reliable than `git`
branch?: string;
commitSha?: string;
commitMessage?: string;
prUrl?: string;
}Git context (branch, commit, PR) is auto-detected from the working tree.
Run
pnpm exec playwright testResults appear in the dashboard within a few seconds of onEnd.
Debug logging
The reporter is quiet by default — only warnings (missing token, upload failures) print to stderr. To see verbose per-test debug output (onTestEnd events, retry attempts, individual API calls), set:
export BRITTLE_DEBUG=1Useful when triaging "test ran but didn't show up in the dashboard" issues. Safe to leave on in CI if you want richer logs.
License
Apache-2.0
