Write E2E Cases
Steps
- •
Review uncommitted git changes to define test scope and target behavior.
- •
Read
e2e/README.mdand follow its conventions. - •
Prefer
@e2e/helpermethods (for exampledev,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 e2eto validate.
Case Structure
- •Include a
srcdirectory in every case (required). - •Add
rsbuild.config.tsonly when needed. - •Split into multiple case directories when cases need different
srccode or different Rsbuild configs.
Constraints
- •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.