Run any Skill in Manus with one click

write-e2e-cases

Stars3,334

Forks269

UpdatedJune 21, 2026 at 07:44

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

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

web-infra-dev

web-infra-dev/rsbuild

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

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

Steps

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, getDistFiles, findFile, getFileContent, expectFile, and expectFileWithContent) to keep tests minimal, including file and file-content assertions.
Add Playwright cases under e2e/cases, following existing directory patterns.
Use short, direct, and stable assertions. Avoid redundant setup and checks.
Run pnpm e2e to validate.

Case Structure

Include a src directory in every case (required).
Prefer putting static Rsbuild configurations in rsbuild.config.ts to enable easier debugging via npx rsbuild.
Use inline config for dynamic values or minor per-test variations.
Split into multiple case directories when cases need different src code or different Rsbuild configs.
For package mocks used by one case, place them under that case's _node_modules directory and call copyNodeModules() before they are resolved.

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.

More from this repository

same repository

release-plugin-package

web-infra-dev/rsbuild

Use when asked to create a release PR for an official Rsbuild plugin package under `packages/plugin-*`, such as `@rsbuild/plugin-react v2.1.0` or `@rsbuild/plugin-sass v2.0.0`.

2026-06-223.3k

rsbuild-performance-profiling

web-infra-dev/rsbuild

Use when profiling, analyzing, reporting, or optimizing Rsbuild performance, including build, dev server, rebuild, static asset serving, memory usage, and CPU profile analysis.

2026-06-223.3k

release-core

web-infra-dev/rsbuild

Use when asked to release `@rsbuild/core` for a specific version.

2026-06-213.3k

add-doc-anchor-ids

web-infra-dev/rsbuild

Align Rspress heading anchor IDs between English and Chinese docs. Use for MDX `\{#...}` anchors, shortened hashes, redundant anchors, or dead links.

2026-06-063.3k

create-draft-release-notes

web-infra-dev/rsbuild

Create or update draft GitHub releases for the current project's main GitHub repository, then organize GitHub-generated release notes into user-friendly sections without rewriting release note items. Use for preparing, formatting, categorizing, creating, or updating GitHub release notes or draft releases, including optional highlights when the user asks for them.

2026-05-213.3k

pr-creator

web-infra-dev/rsbuild

Use when asked to create a pull request for this repository. It helps the PR follow the repository's branch safety rules, title convention, pull request template, and concise English writing style.

2026-04-283.3k

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

Steps

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, getDistFiles, findFile, getFileContent, expectFile, and expectFileWithContent) to keep tests minimal, including file and file-content assertions.
Add Playwright cases under e2e/cases, following existing directory patterns.
Use short, direct, and stable assertions. Avoid redundant setup and checks.
Run pnpm e2e to validate.

Case Structure

Include a src directory in every case (required).
Prefer putting static Rsbuild configurations in rsbuild.config.ts to enable easier debugging via npx rsbuild.
Use inline config for dynamic values or minor per-test variations.
Split into multiple case directories when cases need different src code or different Rsbuild configs.
For package mocks used by one case, place them under that case's _node_modules directory and call copyNodeModules() before they are resolved.

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.