[estefafdez]

What

Adds Beacon (beacon-reporter, MIT) as a reporter, following this article: Beacon: A Better HTML Reporter for Playwright Test Automation.

Beacon generates a static HTML report (beacon-report/) with a dashboard (outcomes, pass-rate trends, slowest tests, flakiness), per-test detail and run-over-run comparison, with no external service required.

Changes

• beacon-reporter added as a devDependency
• Registered as the first reporter in playwright.config.ts (existing reporters untouched)
• beacon-report/ added to .gitignore

How to use

npx playwright test
npx beacon open beacon-report    # serve the report locally
npx beacon export beacon-report  # bundle it into a single HTML file

Verification

Ran the repo's suites locally with the reporter active:

• API project: 21 passed, 1 skipped
• Web project (home, navigation, todo specs): 8 passed, 6 skipped (the navigation suite is describe.skip in the repo)

Screenshots of the generated report:

Dashboard

Test list

Test detail

Notes

• Beacon is a very new package (v0.1.2, first published in October 2026), so it is worth keeping an eye on its releases before relying on it for anything critical.
• CI uploads beacon-report/ as a workflow artifact on every run (name: beacon-report, 30-day retention), so the report is downloadable from any CI run.
• On pushes to main, CI also deploys the report to GitHub Pages: https://estefafdez.github.io/playwright-template/ (Pages is enabled with "GitHub Actions" as the source; the first deploy happens on the next main run after this merges). Pull request runs never deploy.

[github-actions]

Playwright Test Results

52 tests  ±0   32 ✅ ±0   43s ⏱️ +2s
17 suites ±0   20 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 08dabae. ± Comparison against base commit 98d2fdc.

♻️ This comment has been updated with latest results.