test-migration

Plan and execute incremental test suite migrations between frameworks with parallel CI runs.

64|12|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/petrkindlmann/qa-skills --skill test-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-migration
Source: https://github.com/petrkindlmann/qa-skills/tree/main/skills/test-migration
Command: npx skills add https://github.com/petrkindlmann/qa-skills --skill test-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating test suites between frameworks is time-consuming and risky. This Skill provides a structured, incremental approach to migrate tests with parallel CI, preserving coverage and reducing regression risk.

Core Features & Use Cases

  • Incremental migration: move tests module-by-module to minimize risk.
  • Parallel CI strategy: run old and new suites concurrently to validate parity.
  • Migration governance: define mapping patterns, prioritize high-value tests, and decommission old tests safely.
  • Use Case: A team moving from Cypress to Playwright can migrate critical path tests first while keeping the legacy suite running.

Quick Start

Begin by selecting a high-priority subset of tests to migrate and set up a parallel CI workflow that runs both old and new test suites.

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 between frameworks without losing coverage?

Migrating test suites between frameworks without losing coverage requires an incremental approach, moving tests module-by-module. This strategy prioritizes high-value tests and migrates infrastructure first to preserve regression safety and velocity.

What is the best way to run Cypress and Playwright tests in parallel during a migration?

The best way to run Cypress and Playwright tests in parallel during a migration is to execute a parallel CI workflow. Running both old and new suites concurrently validates parity while you incrementally transition critical paths.

How do I manage test migration governance across old and new frameworks?

Manage test migration governance by enforcing mapping patterns for framework translations and prioritizing high-value tests. This structured approach ensures safe parallel execution and governs post-migration decommissioning of legacy suites.

When should I start decommissioning legacy Selenium tests after migrating to a new framework?

Start decommissioning legacy Selenium tests after migrating to a new framework once high-value tests are moved and parity is validated. The process enforces safe post-migration decommissioning after parallel CI runs confirm stability.

Can I migrate critical path tests first while keeping the legacy suite running?

Yes, you can migrate critical path tests first while keeping the legacy suite running. This incremental migration strategy selects a high-priority subset of tests to move while the old suite continues validating overall application stability.