Debug Cucumber HTML Report
Testing & Qualitydebug-cucumber-html-reportDebug Cucumber HTML Report is an Agent Skill for testing & quality published in the vitalets/playwright-bdd repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/vitalets/playwright-bdd/blob/HEAD/.github/skills/debug-cucumber-html-report/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/debug-cucumber-html-report, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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.).