Chromestatus Playwright Testing
Testing & Qualitychromestatus-playwright-testingChromestatus Playwright Testing is an Agent Skill for testing & quality published in the GoogleChrome/chromium-dashboard repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard.
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/GoogleChrome/chromium-dashboard/blob/HEAD/.agents/skills/chromestatus-playwright-testing/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/chromestatus-playwright-testing, 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.
Playwright Testing Skill
This skill provides guidance on how to manage end-to-end tests using Playwright. Use these commands when frontend changes cause visual or functional regressions in the integration tests.
Running Tests
Run all Playwright tests
make pwtests
Run tests in UI mode (Interactive)
Useful for debugging and seeing the browser in action.
make pwtests-ui
Correcting Tests and Updating Snapshots
If your changes are intentional but cause visual regressions (e.g., you updated a CSS style or modified a component's layout), you may need to update the baseline snapshots.
Update Playwright snapshots
make pwtests-update
Debugging
Show test report
If tests fail in CI or locally, you can view a detailed HTML report.
make pwtests-report
Debug a specific test
make pwtests-debug
Best Practices
- Verify Before Submitting: Always run
make pwtestslocally if you change any files inclient-src/elements/ortemplates/. - Review Snapshots: When running
make pwtests-update, carefully review the diffs in the__screenshots__directories to ensure only intended changes are captured. - Shutdown Environment: If the Playwright environment stays active and consumes resources, you can manually shut it down.
make pwtests-shutdown
Reference
- Test Directory: @packages/playwright/tests
- Configuration: @playwright.config.ts
- Build Targets: @Makefile