test-migration

Migrate automated test suites between frameworks while preserving coverage parity.

2|Updated Apr 18, 2021
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill test-migration-rabbicse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-migration
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/test-migration
Command: npx skills add https://github.com/rabbicse/go-projects --skill test-migration-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams migrate automated tests from one framework to another without accidentally shrinking coverage, duplicating flaky behavior, or cutting over too early.

Core Features & Use Cases

  • Incremental framework migration: Rebuild tests one by one instead of doing a risky big-bang rewrite.
  • Parallel CI cutover: Keep legacy and new suites running together until the new suite proves parity.
  • Locator, assertion, and config translation: Convert Selenium, Cypress, Jest, Mocha, and Protractor patterns into Playwright or Vitest equivalents.
  • Use case: A team moving from Cypress to Playwright can modernize locators, preserve auth state, and compare coverage area by area before decommissioning the old suite.

Quick Start

Use the test-migration skill to plan and execute a framework migration for your existing test suite while preserving coverage and running both suites in parallel.

Frequently Asked Questions about test-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate test suites from Selenium to Playwright without losing coverage?

Migrate Selenium test suites to Playwright incrementally by translating locators and assertions, running both suites in parallel, and tracking coverage parity until the legacy suite is safely decommissioned.

What is the best way to handle Cypress to Playwright migration during a CI cutover?

Handle Cypress to Playwright migration by keeping both suites running in parallel CI, modernizing locators, reusing storageState-based authentication, and comparing coverage area by area before decommissioning.

Can I migrate Jest tests to Vitest incrementally instead of doing a big-bang rewrite?

Yes, you can migrate Jest tests to Vitest incrementally, rebuilding tests one by one while running parallel CI cutovers and tracking coverage parity to avoid risky big-bang rewrites.

Does this test migration approach support flaky-test triage for Protractor to Playwright conversions?

Yes, Protractor to Playwright migrations include flaky-test triage, locator translation, assertion translation, and coverage-parity tracking to ensure the new suite is stable before decommissioning.

How do I preserve authentication state when migrating Mocha tests to Vitest?

Preserve authentication state during Mocha to Vitest migrations by utilizing storageState-based authentication reuse, translating assertions, and tracking coverage parity throughout the incremental rewrite.

When should I decommission a legacy test suite after a framework migration?

Decommission a legacy test suite only after the new framework suite proves coverage parity, passing parallel CI cutovers and completing incremental rewrites without duplicating flaky behavior.