⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Jest/Vitest 迁移到 Rstest 指南：自动化测试框架迁移工具与最佳实践

migrate-to-rstest by rstackjs/agent-skills

94 周安装量

51 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/rstackjs/agent-skills --skill migrate-to-rstest

自动化测试 Rust

🇨🇳中文介绍

迁移至 Rstest

目标

将以 Jest 或 Vitest 为基础的测试及其配置迁移到 Rstest，并尽可能减少行为变更。

迁移原则（必须遵守）

最小变更优先：优先采用能够恢复测试通过的最小可行变更。
配置优于代码：优先在配置/工具/模拟中修复，而非修改测试逻辑。
不改变用户源代码行为：除非用户明确要求，否则避免修改生产/业务源代码文件。
避免批量重写测试：如果局部兼容性补丁可以解决问题，则不要重构整个测试套件。
保留测试意图：保持断言和场景覆盖范围不变，除非明显因框架差异而失效。
延迟移除旧测试运行器：在迁移期间保留 Jest/Vitest 依赖项和旧配置；仅在 Rstest 测试通过后才移除。

工作流程

检测当前测试框架 (references/detect-test-framework.md)
打开官方迁移指南：
- Jest: https://rstest.rs/guide/migration/jest.md
- Vitest: https://rstest.rs/guide/migration/vitest.md
- 优先使用 .md 格式的 URL；Rstest 页面提供了对 AI 更友好的 Markdown 变体。
依赖安装门控（阻塞检查，参见 references/dependency-install-gate.md）

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

1. 检测当前测试框架

使用 references/detect-test-framework.md。如果同时存在 Jest 和 Vitest，请一次迁移一个作用域（包/套件），在 Rstest 上每个作用域测试通过之前保持混合模式。

3. 依赖安装门控（阻塞检查）

在大规模编辑之前，请验证依赖项可以安装且测试运行器二进制文件可用。详细的检查项、阻塞模式输出格式和 ni 策略位于：references/dependency-install-gate.md

补丁作用域策略（严格）

CLI/脚本/配置迁移 (package.json, rstest.config.ts, include/exclude, test environment)。
测试设置适配器迁移（例如，从 @testing-library/jest-dom/vitest 迁移到 Rstest 中基于匹配器的设置）。
模拟兼容性调整（目标模块路径, { mock: true }, importActual）。
针对单个测试的局部设置修复（单文件、单套件级别）。
测试/设置辅助函数中的路径解析兼容性修复 (import.meta.url 与 __dirname)。
作为最后手段，修改测试主体。
默认情况下绝不修改运行时源代码逻辑。

在未首先证明配置级修复不足的情况下，不要一次性重写大量测试。
不要为了满足测试而改变业务/运行时行为。
不要仅仅为了让测试通过而改变断言语义。
不要将迁移范围扩大到 monorepo 中不相关的包。
在确认 Rstest 测试通过之前，不要删除旧测试运行器的依赖项/配置。

大规模编辑的升级规则

如果修复需要满足以下任一条件：

编辑许多测试文件，或
更改用户源文件，

请停止并提供：

最小化修复失败的原因，
建议的大规模变更选项，
每个选项的预期影响/风险，
推荐选项。

6. 运行测试并修复增量问题

运行测试套件并迭代修复失败项。
首先修复配置和解析器错误，然后处理模拟/计时器/快照，最后才触及测试逻辑。
如果在 Rspack 下重新导出的模块模拟失败，请首先检查项目是否固定使用 rstest < 0.9.3。
在进行广泛的测试重写之前，请检查已知陷阱：references/rstest-compat-pitfalls.md

提供简洁的变更摘要并列出涉及的文件。
指出任何剩余的手动步骤或待办事项。

🇺🇸English

Migrate to Rstest

Goal

Migrate Jest- or Vitest-based tests and configuration to Rstest with minimal behavior changes.

Migration principles (must follow)

Smallest-change-first : prefer the smallest viable change that restores test pass.
Config before code : prefer fixing in config/tooling/mocks before touching test logic.
Do not change user source behavior : avoid modifying production/business source files unless user explicitly requests it.
Avoid bulk test rewrites : do not refactor entire test suites when a local compatibility patch can solve it.
Preserve test intent : keep assertions and scenario coverage unchanged unless clearly broken by framework differences.
Defer legacy runner removal : keep Jest/Vitest dependency and legacy config during migration; remove only after Rstest tests pass.

Workflow

Detect current test framework (references/detect-test-framework.md)
Open the official migration guide(s):
- Jest: https://rstest.rs/guide/migration/jest.md
- Vitest: https://rstest.rs/guide/migration/vitest.md
- Prefer the .md URL form when available; Rstest pages provide Markdown variants that are more AI-friendly.
Dependency install gate (blocker check, see references/dependency-install-gate.md)
Apply framework-specific migration deltas:
- Jest: references/jest-migration-deltas.md
- Vitest: references/vitest-migration-deltas.md
- Global API replacement rules: references/global-api-migration.md
- Known compatibility pitfalls: references/rstest-compat-pitfalls.md
Check type errors
Run tests and fix deltas
Remove legacy test runner dependency/config only after Rstest is green
Summarize changes

1. Detect current test framework

Use references/detect-test-framework.md. If both Jest and Vitest are present, migrate one scope at a time (package/suite), keeping mixed mode until each scope is green on Rstest.

3. Dependency install gate (blocker check)

Before large-scale edits, verify dependencies can be installed and test runner binaries are available. Detailed checks, blocked-mode output format, and ni policy are in: references/dependency-install-gate.md

Patch scope policy (strict)

Preferred change order

CLI/script/config migration (package.json, rstest.config.ts, include/exclude, test environment).
Test setup adapter migration (for example @testing-library/jest-dom/vitest to matcher-based setup in Rstest).
Mock compatibility adjustments (target module path, { mock: true }, importActual).
Narrow per-test setup fixes (single-file, single-suite level).
Path resolution compatibility fixes (import.meta.url vs __dirname) in test/setup helpers.
As a last resort, test body changes.
Never modify runtime source logic by default.

Red lines

Do not rewrite many tests in one sweep without first proving config-level fixes are insufficient.
Do not alter business/runtime behavior to satisfy tests.
Do not change assertion semantics just to make tests pass.
Do not broaden migration to unrelated packages in monorepo.
Do not delete legacy runner dependency/config before confirming Rstest tests pass.

Escalation rule for large edits

If a fix would require either:

editing many test files, or
changing user source files,

stop and provide:

why minimal fixes failed,
proposed large-change options,
expected impact/risk per option,
recommended option.

6. Run tests and fix deltas

Run the test suite and fix failures iteratively.
Fix configuration and resolver errors first, then address mocks/timers/snapshots, and touch test logic last.
If mocks fail for re-exported modules under Rspack, first check whether the project is pinned to rstest < 0.9.3.
Before broad test rewrites, check known pitfalls in: references/rstest-compat-pitfalls.md

8. Summarize changes

Provide a concise change summary and list files touched.
Call out any remaining manual steps or TODOs.

Weekly Installs

Repository

rstackjs/agent-skills

GitHub Stars

First Seen

Feb 26, 2026

Security Audits

Gen Agent Trust HubWarn SocketPass SnykWarn

Installed on

codex66

cursor63

kimi-cli61

gemini-cli61

amp61

cline61

Skills CLI 使用指南：AI Agent 技能包管理器安装与管理教程

50,200 周安装