Name: Write E2e Cases
Author: web-infra-dev

name	write-e2e-cases
description	Use when adding or updating Rsbuild end-to-end tests in `e2e/cases`, including new feature coverage, bug reproduction, and regression prevention.

Write E2E Cases

Review uncommitted git changes to define test scope and target behavior.
Read e2e/README.md and follow its conventions.
Prefer @e2e/helper methods (for example dev, build) to keep tests minimal.
Add Playwright cases under e2e/cases, following existing directory patterns.
Keep assertions focused and readable; avoid redundant setup and checks.
Run pnpm e2e to validate.

Include a src directory in every case (required).
Add rsbuild.config.ts only when needed.
Split into multiple case directories when cases need different src code or different Rsbuild configs.

If tests can pass only after source-code changes, do not change source code directly. Explain the required source change and ask the user before proceeding.

name	write-e2e-cases
description	Use when adding or updating Rsbuild end-to-end tests in `e2e/cases`, including new feature coverage, bug reproduction, and regression prevention.

Review uncommitted git changes to define test scope and target behavior.
Read e2e/README.md and follow its conventions.
Prefer @e2e/helper methods (for example dev, build) to keep tests minimal.
Add Playwright cases under e2e/cases, following existing directory patterns.
Keep assertions focused and readable; avoid redundant setup and checks.
Run pnpm e2e to validate.

Include a src directory in every case (required).
Add rsbuild.config.ts only when needed.
Split into multiple case directories when cases need different src code or different Rsbuild configs.

If tests can pass only after source-code changes, do not change source code directly. Explain the required source change and ask the user before proceeding.

write-e2e-cases