Run any Skill in Manus with one click

write-e2e-cases

Stars1,139

Forks98

UpdatedJune 1, 2026 at 09:07

Use when adding or updating Rsdoctor 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/rsdoctor

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 Rsdoctor end-to-end tests in `e2e/cases/`, including new feature coverage, bug reproduction, and regression prevention.

Write E2E Cases

Rsdoctor E2E tests use Playwright and live under e2e/cases/. Each bundler has its own directory:

e2e/cases/doctor-rspack/ — tests using Rspack compilation
e2e/cases/doctor-rsbuild/ — tests using Rsbuild
e2e/cases/doctor-rspeedy/ — tests using Rspeedy

Steps

Review uncommitted git changes to define test scope and target behavior.
Read e2e/README.md and follow its conventions.
Use helpers from @scripts/test-helper (for example compileByRspack) to compile fixtures. Do not call bundler APIs directly.
Add Playwright test files under the appropriate e2e/cases/doctor-* directory, following existing patterns.
Test fixtures (source files, loaders, configs) go in fixtures/ subdirectories inside each case directory.
Keep assertions focused and readable; avoid redundant setup and checks.
Run pnpm e2e from the repository root to validate.

Case Structure

Each test file creates an Rsdoctor plugin instance (e.g., createRsdoctorPlugin from a local test-utils.ts), compiles a fixture via compileByRspack, and asserts on the SDK store data.
Fixtures are plain JS/TS files and loaders in fixtures/ — not full application directories.
Use @rsdoctor/core/plugins for getSDK / setSDK when inspecting analysis results.

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

pr-creator

web-infra-dev/rsdoctor

Use when asked to create a pull request for the Rsdoctor repository. Ensures the PR follows branch safety rules, Conventional Commits title convention, the project's PR template, and concise English writing style.

2026-05-211.1k

create-draft-release-notes

web-infra-dev/rsdoctor

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.

2026-05-131.1k

code-reviewer

web-infra-dev/rsdoctor

Review code changes like a pragmatic senior engineer — focus on functional bugs, regressions, type-safety, and missing tests. Use when performing code reviews on PRs or diffs in the rsdoctor repository.

2026-04-101.1k

docs-en-improvement

web-infra-dev/rsdoctor

Improve English documentation under `packages/document/docs/en` by rewriting unnatural translated sentences into clear, professional English while preserving meaning. Use when editing or polishing English docs in the Rsdoctor project.

2026-04-101.1k

release-rsdoctor

web-infra-dev/rsdoctor

Use when asked to release Rsdoctor packages for a specific version. All `@rsdoctor/*` packages (except `@rsdoctor/mcp-server`) are versioned together via changesets.

2026-04-101.1k

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

Write E2E Cases

Rsdoctor E2E tests use Playwright and live under e2e/cases/. Each bundler has its own directory:

e2e/cases/doctor-rspack/ — tests using Rspack compilation
e2e/cases/doctor-rsbuild/ — tests using Rsbuild
e2e/cases/doctor-rspeedy/ — tests using Rspeedy

Steps

Review uncommitted git changes to define test scope and target behavior.
Read e2e/README.md and follow its conventions.
Use helpers from @scripts/test-helper (for example compileByRspack) to compile fixtures. Do not call bundler APIs directly.
Add Playwright test files under the appropriate e2e/cases/doctor-* directory, following existing patterns.
Test fixtures (source files, loaders, configs) go in fixtures/ subdirectories inside each case directory.
Keep assertions focused and readable; avoid redundant setup and checks.
Run pnpm e2e from the repository root to validate.

Case Structure

Each test file creates an Rsdoctor plugin instance (e.g., createRsdoctorPlugin from a local test-utils.ts), compiles a fixture via compileByRspack, and asserts on the SDK store data.
Fixtures are plain JS/TS files and loaders in fixtures/ — not full application directories.
Use @rsdoctor/core/plugins for getSDK / setSDK when inspecting analysis results.

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.