Run any Skill in Manus with one click

migrate-to-rstest

Stars78

Forks1

UpdatedJune 23, 2026 at 08:03

Migrate Jest or Vitest projects to Rstest. Use when asked to move from Jest/Vitest to Rstest, replace `jest`/`vi` APIs with `@rstest/core`, translate config into `rstest.config.ts`, update scripts/coverage/setup/mocks/snapshots/projects, or diagnose migration failures caused by Rstest's Rsbuild/Rspack execution model or version skew.

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

rstackjs

rstackjs/agent-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

File Explorer

6 files

SKILL.md

readonly

name	migrate-to-rstest
description	Migrate Jest or Vitest projects to Rstest. Use when asked to move from Jest/Vitest to Rstest, replace `jest`/`vi` APIs with `@rstest/core`, translate config into `rstest.config.ts`, update scripts/coverage/setup/mocks/snapshots/projects, or diagnose migration failures caused by Rstest's Rsbuild/Rspack execution model or version skew.

Migrate to Rstest

Goal

Migrate Jest/Vitest tests and config to Rstest with minimal behavior changes. Use the current Rstest migration docs for exact mappings; this skill adds scope, dependency, and cleanup guardrails.

Workflow

Detect runner and scope (references/detect-test-framework.md).
Run dependency/version gates (references/dependency-install-gate.md).
Read only the needed deltas: Jest, Vitest, and/or global API replacement.
Migrate scripts/config/setup before tests; prefer adapters or Rsbuild/Rspack config fixes before editing test bodies.
Validate discovery/types/run, fixing failures in this order: dependency skew, config/resolver, setup/env/coverage, mocks/timers/snapshots, test bodies.
After the scope is green, remove only scope-local legacy files and devDeps no remaining scope uses.
Summarize changes, kept legacy files, unsupported fields, and TODOs.

Guardrails

Keep the smallest viable scope; do not broaden a monorepo migration or bulk-rewrite tests when config/setup fixes are plausible.
Do not change production behavior, assertions, test names, scenarios, or coverage thresholds to make migration pass.
No jest/vi shims or aliases; rewrite call sites to Rstest APIs (references/global-api-migration.md).
Do not silently drop unknown config fields; verify or report them as unsupported.

High-risk Rstest deltas

rstest / rstest run is single-run; watch mode is rstest --watch or rstest watch.
globals defaults to false; if globals remain, set globals: true and add @rstest/core/globals types.
Rstest runs on Rsbuild/Rspack. Use references/dependency-install-gate.md for latest-only APIs, coverage providers, adapters, plugins, and toolchain-version fallbacks.

Escalate before large edits

If the next fix requires many test edits or production source changes, stop and report: why smaller fixes failed, options, risks, and the recommended path.

More from this repository

same repository

rstack-eco-ci-debug

rstackjs/agent-skills

Debug Rstack ecosystem CI failures and attribute the real source PR or downstream change. Always use this skill when the user mentions Rspack eco-ci, rstack-ecosystem-ci, a suite turning red, a downstream regression, a green-to-red pivot, canary bisect, @rspack-canary/core, or daily eco-ci triage — even if they only ask "why is this suite failing", "which PR broke it", or "is this Rspack's fault". Use it to avoid over-blaming the first Rspack commit that appears red in status data.

2026-06-2678

release-blog-writer

rstackjs/agent-skills

Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement.

2026-06-2678

create-draft-release-notes

rstackjs/agent-skills

Create or update draft GitHub release notes, or output organized Markdown when draft creation is unavailable. Use for release notes, draft releases, release PR checks, npm staged publishing checks, and optional highlights.

2026-06-2578

rspress-docs-generator

rstackjs/agent-skills

Generate or maintain Rspress documentation for a project. Use whenever the user wants to create a new Rspress v2 docs site, add docs for user-facing feature work or PRs, maintain a dedicated Rspress docs project in a monorepo, or prevent stale Rspress v1 scaffolds/version drift before documentation work. For full v1-to-v2 migration, hand off to the rspress-v2-upgrade skill.

2026-06-2578

rstack-repo-maintain

rstackjs/agent-skills

Audit and modernize RstackJS/Rspack ecosystem repositories to the current shared infrastructure baseline: Rslib ESM or dual builds, Rslint recommended rules, Rstest test tooling, Node 20+ support where appropriate, TypeScript 6 and tsgo where compatible, concise README/AGENTS docs, release workflow cleanup, unused dependency removal, and infra PR commit conventions. Use when updating rstackjs repositories, copying infra patterns from maintained exemplars, or reviewing package/tooling consistency.

2026-06-2478

pr-creator

rstackjs/agent-skills

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-06-2478

name	migrate-to-rstest
description	Migrate Jest or Vitest projects to Rstest. Use when asked to move from Jest/Vitest to Rstest, replace `jest`/`vi` APIs with `@rstest/core`, translate config into `rstest.config.ts`, update scripts/coverage/setup/mocks/snapshots/projects, or diagnose migration failures caused by Rstest's Rsbuild/Rspack execution model or version skew.

Migrate to Rstest

Goal

Migrate Jest/Vitest tests and config to Rstest with minimal behavior changes. Use the current Rstest migration docs for exact mappings; this skill adds scope, dependency, and cleanup guardrails.

Workflow

Detect runner and scope (references/detect-test-framework.md).
Run dependency/version gates (references/dependency-install-gate.md).
Read only the needed deltas: Jest, Vitest, and/or global API replacement.
Migrate scripts/config/setup before tests; prefer adapters or Rsbuild/Rspack config fixes before editing test bodies.
Validate discovery/types/run, fixing failures in this order: dependency skew, config/resolver, setup/env/coverage, mocks/timers/snapshots, test bodies.
After the scope is green, remove only scope-local legacy files and devDeps no remaining scope uses.
Summarize changes, kept legacy files, unsupported fields, and TODOs.

Guardrails

Keep the smallest viable scope; do not broaden a monorepo migration or bulk-rewrite tests when config/setup fixes are plausible.
Do not change production behavior, assertions, test names, scenarios, or coverage thresholds to make migration pass.
No jest/vi shims or aliases; rewrite call sites to Rstest APIs (references/global-api-migration.md).
Do not silently drop unknown config fields; verify or report them as unsupported.

High-risk Rstest deltas

rstest / rstest run is single-run; watch mode is rstest --watch or rstest watch.
globals defaults to false; if globals remain, set globals: true and add @rstest/core/globals types.
Rstest runs on Rsbuild/Rspack. Use references/dependency-install-gate.md for latest-only APIs, coverage providers, adapters, plugins, and toolchain-version fallbacks.

Escalate before large edits

If the next fix requires many test edits or production source changes, stop and report: why smaller fixes failed, options, risks, and the recommended path.