Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

write-e2e-cases

Estrelas3.334

Forks269

Atualizado21 de junho de 2026 às 07:44

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

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

web-infra-dev

web-infra-dev/rsbuild

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·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.

Mais deste repositório

mesmo repositório

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.