skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
rstackjs/agent-skills436 installs

migrate-to-rstest

Migrate Jest, Vitest, or Playwright Test to Rstest while preserving test discovery, assertions, mocks, snapshots, and coverage.

How do I install this agent skill?

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

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill is a comprehensive guide for migrating JavaScript and TypeScript test suites from frameworks like Jest, Vitest, and Playwright to Rstest. It employs secure practices such as using native package managers, verifying official documentation, and maintaining test parity. A low-risk surface for indirect prompt injection was identified because the skill processes external test code and configuration files and has the authority to write files and execute terminal commands.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

  • Runlayerwarn

    3/8 files flagged

  • ZeroLeakspass

    Score: 93/100 · 2 sections analyzed

What does this agent skill do?

<!-- cspell:words TYPELESS -->

Migrate to Rstest

Goal

Migrate the smallest runnable Jest, Vitest, or Playwright Test scope with minimal behavior change. Use documentation and types that match the installed Rstest version; use latest online docs only after the capability gate confirms they apply.

Workflow

  1. Detect the runner, environment, Rstack integration, and smallest runnable scope with references/detect-test-framework.md.
  2. Run references/dependency-install-gate.md before choosing Rstest, coverage, adapter, or plugin APIs.
  3. Before editing, record the exact command, Node and runner versions, environment, files/tests/skips/snapshots, and failures. Capture the pre-migration test manifest and follow references/discovery-parity.md throughout the migration.
  4. For Jest read references/jest-migration-deltas.md; for Vitest read references/vitest-migration-deltas.md; for global APIs also read references/global-api-migration.md; for a detected Playwright Test runner read references/playwright-migration-deltas.md. Do not load the Playwright path for a browser-only request whose runner is not Playwright Test. Migrate scripts, config, and setup before editing test bodies; prefer adapter or Rsbuild/Rspack fixes over broad test rewrites.
  5. If config loading emits [MODULE_TYPELESS_PACKAGE_JSON], use references/config-module-type.md. Do not suppress the warning or change the whole package module type without an audit.
  6. Get the migrated scope semantically green. Fix failures in this order: dependency skew, config/resolver, discovery, setup/environment/coverage, mocks/timers/snapshots, then test bodies.
  7. Compare the post-migration manifest and execution counts with the baseline. Classify every added, removed, skipped, or excluded test explicitly; do not call a run equivalent merely because it is green. For Jest snapshot migrations, also complete the snapshot cleanup and unchecked validation in references/jest-migration-deltas.md.
  8. Remove temporary aliases, diagnostic hooks, and copied legacy workarounds that are no longer required. Keep only configuration proven necessary by behavior or measurement.
  9. If the migration misses its performance target or regresses in wall time, build time, test runtime, output volume, or memory, follow rstest-debugging when available. Otherwise use references/performance-diagnosis.md. If repeated worker startup or per-file dependency compilation dominates, use the pool comparison in that workflow to evaluate vmForks or vmThreads.
  10. After correctness and performance validation, remove only legacy files and dependencies owned by the migrated scope. Summarize behavior parity, discovery differences, unsupported fields, retained compatibility config, performance tradeoffs, and TODOs.

Guardrails

  • Keep the smallest viable scope. Do not broaden a monorepo migration because scopes share a lockfile.
  • Do not change production behavior, assertions, test names, scenarios, coverage thresholds, or ignore directives to make migration pass.
  • Do not introduce jest/vi shims or aliases; rewrite call sites with references/global-api-migration.md.
  • Do not silently drop unknown config fields or historical excludes. Verify, replace, or report each one.
  • Compare the same test manifest under the same Node version, coverage mode, and cache conditions. Change one tuning option at a time and keep worker settings fixed unless testing that option.
  • Keep the previous runner until Rstest is green. Use a local Rstest checkout only for labeled diagnostics, then validate the final result with the project's installed dependency.
  • Escalate before many test edits or any production-source change: report why smaller config/setup fixes failed, options, risks, and the recommended path.

High-risk Rstest deltas

  • rstest / rstest run is single-run; watch mode is rstest --watch or rstest watch.
  • globals defaults to false; preserving global APIs requires globals: true and @rstest/core/globals types.
  • Rstest builds before tests run. rs.mock() is runtime replacement and does not by itself prune the real module graph.
  • Dependency bundling trades compiler work for runtime Node loading. Neither “bundle all” nor “externalize all” is universally faster; measure a representative file and the full scope.
  • An externalized runtime mock must match the exact request and module format. A config-wide external is unsafe when any test needs the real module.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/rstackjs/agent-skills/migrate-to-rstest">View migrate-to-rstest on skillZs</a>