Playwright / Scenario
Rebuild the Reporting Signal
Turn a noisy, fragmented test-reporting pipeline into useful local feedback, mergeable CI evidence, and actionable ownership data.
- Difficulty
- Medium
- Format
- Scenario
- Points
- 150
- Estimate
- 13 min
// MISSION BRIEF
Your Mission
An organization has plenty of test output but little usable signal. Read its current configuration, shard workflow, and triage complaints. Make reporting choices that support developers, reviewers, and release automation.
// FIRST CONTACT
Battle teaser
First artifact
playwright.config.ts
What is the strongest local and CI reporter split for these consumers?
- AGenerate a separate HTML report inside each shard and keep none of them as artifacts
- BKeep list as the only reporter everywhere and reconstruct a combined result from console logs later, since reviewers might be able to infer shard context manually
- CDisable reporters so traces become smaller
- DUse list locally; emit blob reports on CI shards, merge once to HTML, and set open to never
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
playwright-reportingci-artifactscustom-reporterplaywright