# Chromestatus Playwright Testing

> Guidance for running, debugging, and updating Playwright end-to-end tests in chromium-dashboard. Use when this capability is needed.

- Skill: `tomevault-io/chromestatus-playwright-testing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/chromestatus-playwright-testing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/chromestatus-playwright-testing/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/chromestatus-playwright-testing

---


# 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
```bash
make pwtests
```

### Run tests in UI mode (Interactive)
Useful for debugging and seeing the browser in action.
```bash
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
```bash
make pwtests-update
```

## Debugging

### Show test report
If tests fail in CI or locally, you can view a detailed HTML report.
```bash
make pwtests-report
```

### Debug a specific test
```bash
make pwtests-debug
```

## Best Practices
1. **Verify Before Submitting**: Always run `make pwtests` locally if you change any files in `client-src/elements/` or `templates/`.
2. **Review Snapshots**: When running `make pwtests-update`, carefully review the diffs in the `__screenshots__` directories to ensure only intended changes are captured.
3. **Shutdown Environment**: If the Playwright environment stays active and consumes resources, you can manually shut it down.
```bash
make pwtests-shutdown
```

## Reference
- **Test Directory**: @packages/playwright/tests
- **Configuration**: @playwright.config.ts
- **Build Targets**: @Makefile

---
> Source: [GoogleChrome/chromium-dashboard](https://github.com/GoogleChrome/chromium-dashboard) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-29 -->