🎭Playwright Reporter
A Playwright reporter for M00N Report. Streams test results to the dashboard in real time, uploads screenshots, videos, and traces captured by Playwright, and tracks test.step calls and native retry attempts without any test-side instrumentation.
Features
Test results stream to the dashboard via WebSocket as each test completes.
Calls to test.step() are captured automatically and streamed live.
Screenshots, videos, traces, and custom testInfo.attach() artifacts are uploaded.
Each Playwright retry attempt is recorded as a separate execution row.
Link autotests to manual cases via the caseId annotation, [TC-N] tokens in titles, or dashboard auto-link rules.
First-class integration with Playwright Test and the native reporter API.
Launches carry tags, custom attributes, and CI/CD context for organization-wide reporting.
Safe under Playwright's worker-based parallelism - no shared mutable state.
AI Setup Prompt
A complete, self-contained prompt for integrating this reporter into an existing Playwright TypeScript project using an AI assistant. The prompt covers installation, playwright.config.ts changes, environment variables, step and retry usage, and the most common integration pitfalls.
apiKey from process.env.M00N_API_KEY and configure the secret in CI or a local .env file that is listed in .gitignore.Configuration Reference
| Option | Type | Default | Description |
|---|---|---|---|
serverUrl | string | - | Required. M00N ingest service URL (e.g. https://m00nreport.com) |
apiKey | string | - | Required. Project API key (identifies org and project) |
enabled | boolean | true | Enable or disable the reporter. Also accepts M00N_ENABLED env var. |
launch | string | - | Custom name or title for this test run. |
tags | string[] | [] | Tags applied to the launch and visible on the dashboard. |
attributes | object | {} | Custom key-value metadata. Recognized CI/CD keys feed the CI context banner; all others render as badges. |
debug | boolean | false | Enable verbose reporter logging. Also accepts M00N_DEBUG env var. |
CI/CD Context Banner
When CI/CD-related attribute keys are passed through the attributesoption, M00N Report automatically displays them in a dedicated CI context banner at the top of the launch view. Any attributes that do not match the keys below are rendered as regular attribute badges.
Recognized CI Attribute Keys
| Banner Field | Accepted Keys (case-insensitive) | Example Value |
|---|---|---|
| Pipeline | pipeline, GITHUB_WORKFLOW, CI_PIPELINE_NAME, JOB_NAME | Deploy Production |
| Branch | branch, git_branch, GITHUB_REF, CI_COMMIT_REF_NAME, BRANCH_NAME | main |
| Commit | commit, git_commit, GITHUB_SHA, CI_COMMIT_SHA, GIT_COMMIT | a1b2c3d (truncated to 7 chars) |
| Build # | build_number, GITHUB_RUN_NUMBER, CI_PIPELINE_ID, BUILD_NUMBER | 1234 |
| Build URL | build_url, GITHUB_SERVER_URL, CI_PIPELINE_URL, BUILD_URL | https://github.com/... (clickable) |
| Environment | environment, env, DEPLOY_ENV | staging |
| Trigger | trigger, GITHUB_EVENT_NAME, CI_PIPELINE_SOURCE | push |
branch and GITHUB_REF populate the Branch field of the CI banner. Only the first match per field is used.Concepts
Reference documentation for each subsystem of the reporter: attachment handling, retry tracking, step tracking, configuration sources, and troubleshooting.