Browser regression suite
Turn the application's most important behavior into repeatable browser tests.
Customize the recipe
0/1500 characters
Prompt preview
# Browser regression suite Turn the application's most important behavior into repeatable browser tests. ## Deliverable A focused test suite and local execution instructions with stable fixtures. ## Stack and visual direction - Recommended starting stack: Use the existing stack, browser tooling and the project's test commands. Capture before-and-after evidence. - Minimalism: Use deliberate spacing, a compact palette and a clear typographic hierarchy. Retain the labels, feedback and affordances people need to act. Use this direction for any new or revised UI within the agreed patch scope. ## Tools and setup · Universal Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have. Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment. - [Playwright CLI](https://github.com/microsoft/playwright-cli) (Skill) — Walk real browser interactions and collect screenshots or evidence for regressions. Node.js and supported browser binaries. Use a local build or authorized test environment. [Official setup](https://github.com/microsoft/playwright-cli#readme). Fallback: Walk the same primary journey in a local browser and record the viewport, actions and outcomes. - [Playwright Test](https://github.com/microsoft/playwright) (Repository) — Automate repeatable browser journeys using visible roles and assertions. Playwright-managed browser binaries. [Official setup](https://playwright.dev/docs/intro). - [Mock Service Worker](https://github.com/mswjs/msw) (Repository) — Build repeatable network fixtures for loading, error, empty and success scenarios. ## Workflow 1. Choose the highest-risk task paths and represent them with controlled fixtures. Cover a success, failure and recovery path, and use role-based locators and condition-driven assertions. 2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable. 3. Run the applicable checks and report what actually passed along with any checks you could not run. ## Acceptance checks - [ ] Tests pass on two repeated runs with isolated data. - [ ] A controlled failure in a critical path produces a visible, actionable test failure. - [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess. - [ ] Capture a reproducible baseline, validate the changed flow afterward, and report evidence and any findings still open.
Recipe resources
Source, setup, and compatibility details.
Playwright CLI
Walk real browser interactions and collect screenshots or evidence for regressions.
Node.js and supported browser binaries. Use a local build or authorized test environment.
License · Apache-2.0
Setup guide for Playwright CLIPlaywright Test
Automate repeatable browser journeys using visible roles and assertions.
Playwright-managed browser binaries.
License · Apache-2.0
Setup guide for Playwright TestMock Service Worker
Build repeatable network fixtures for loading, error, empty and success scenarios.
License · MIT
Compound Engineering
Plan a substantial change, review the implementation and capture durable project knowledge.
Use the installation instructions for the receiving agent.
Upstream documents Codex, Claude Code, Antigravity.
Setup guide for Compound Engineering