# Debug Cucumber HTML Report

> Debug or inspect the Cucumber HTML reporter output in the playwright-bdd project. Use when: investigating DOM structure changes in the Cucumber HTML reporter, updating test selectors or POMs after reporter upgrades, verifying what attachments/hooks/steps look like in the generated HTML report.

- Skill: `vitalets/debug-cucumber-html-report` (Agent Skill)
- Install (CLI): `npx skillmds@latest add vitalets/debug-cucumber-html-report`
- Raw SKILL.md: https://api.skillmd.com/api/skills/vitalets/debug-cucumber-html-report/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: vitalets (https://skillmd.com/u/vitalets)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/vitalets/debug-cucumber-html-report

---


# Debug Cucumber HTML Report

## When to Use
- Inspecting the Cucumber HTML report DOM structure after a reporter version upgrade
- Updating test selectors in `check-report`
- Verifying how steps, hooks, attachments, screenshots, traces appear in the report

## Opening the Report

Always use **`playwright-cli`** with the `PLAYWRIGHT_MCP_ALLOW_UNRESTRICTED_FILE_ACCESS` environment variable to open local report files. Do NOT use Playwright MCP (`@playwright/mcp`).

Run `playwright-cli --help` to see the full list of available commands (open, snapshot, eval, click, goto, etc.).