with one click
chromestatus-playwright-testing
// Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard.
// Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard.
How to add a new field to a feature across the entire stack (Data, API, and Frontend).
Guidance for working on the Flask-based backend, NDB Datastore, and OpenAPI integrations in chromium-dashboard.
Guidance for local verification of changes to ensure they pass CI checks (linting, type checking, testing, and building).
Guidance for working on the Lit-based frontend, Shoelace widgets, and client-side routing in chromium-dashboard.
| name | chromestatus-playwright-testing |
| description | Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard. |
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.
make pwtests
Useful for debugging and seeing the browser in action.
make pwtests-ui
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.
make pwtests-update
If tests fail in CI or locally, you can view a detailed HTML report.
make pwtests-report
make pwtests-debug
make pwtests locally if you change any files in client-src/elements/ or templates/.make pwtests-update, carefully review the diffs in the __screenshots__ directories to ensure only intended changes are captured.make pwtests-shutdown