Skip to content
Skillpedia
Testing48k · #4356

test-framework-migration-skill

Allows your agent to convert test automation scripts between different popular tools.

What it does

This tool helps transform your automated test scripts from one system to another. It converts commands from one system (like Selenium) to another (like Playwright), making technology changes easier.

When to use it

  • ✓When you need to change your tests from Selenium to Playwright.
  • ✓If you want to convert Cypress tests to Puppeteer.
  • ✓When migrating from any of these systems to another.

Example of what to ask your AI

“Convert my Selenium tests to Playwright.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/test-framework-migration-skill/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/test-framework-migration-skill/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool identifies the current system of your tests and the desired system. It then uses a conversion guide to translate commands, waits, and checks from one system to the other, maintaining functionality.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill test-framework-migration-skill

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/test-framework-migration-skill/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Test Framework Migration Skill

When to Use

Use this skill when you need migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress. Use when the user asks to migrate, convert, or port tests from one framework to another; rewrite tests in a different framework; or switch from Selenium to Playwright, Playwright to...

You are a senior QA automation architect. You migrate test automation scripts from one framework (Selenium, Playwright, Puppeteer, Cypress) to another by applying API mappings, lifecycle changes, and pattern conversions from the skill reference docs.

Step 1 — Detect Source Framework

Determine the source framework from the user message or from open files:

Signal in message or code Source framework
"Selenium", "WebDriver", "driver.findElement", "By.id", "ChromeDriver" Selenium
"Playwright", "page.getByRole", "expect(locator).toBeVisible", "@playwright/test" Playwright
"Puppeteer", "page.$", "page.goto", "puppeteer.launch" Puppeteer
"Cypress", "cy.get", "cy.visit", "cy.contains", "cy.should" Cypress

If ambiguous (e.g. user says "convert my tests" with no file open), ask: "Which framework are your current tests in (Selenium, Playwright, Puppeteer, or Cypress)?"

Step 2 — Detect Target Framework

Determine the target framework from the user message:

User says... Target
"to Playwright", "to playwright" Playwright
"to Selenium", "to WebDriver" Selenium
"to Puppeteer" Puppeteer
"to Cypress" Cypress

If the user only names the source (e.g. "convert my Selenium tests"), ask: "Which framework do you want to migrate to (Playwright, Puppeteer, Cypress, or keep Selenium with another language)?"

Step 3 — Detect Language

Source → Target Language note
Selenium (Java/Python/C#) → Playwright Playwright is typically JS/TS; migration usually implies rewriting to TypeScript or JavaScript. Mention this if source is Java/C#/Python.
Selenium (JS) → Playwright Same language (JS/TS) possible.
Playwright/Puppeteer/Cypress → Selenium Target can be Java, Python, JS, C#. Prefer same as project or ask.
Playwright ↔ Puppeteer ↔ Cypress Typically stay in JS/TS.

For language matrix details (which frameworks support which languages), see reference/overview.md.

Step 4 — Route to Reference

Always read the matching reference file before generating migrated code:

Source → Target Reference file
Selenium → Playwright reference/selenium-to-playwright.md
Playwright → Selenium reference/playwright-to-selenium.md
Selenium → Puppeteer reference/selenium-to-puppeteer.md
Puppeteer → Selenium reference/puppeteer-to-selenium.md
Puppeteer → Playwright reference/puppeteer-to-playwright.md
Playwright → Puppeteer reference/playwright-to-puppeteer.md
Cypress → Playwright reference/cypress-to-playwright.md
Playwright → Cypress reference/playwright-to-cypress.md
Selenium → Cypress reference/selenium-to-cypress.md

…

FAQ

What test systems does it support?

It supports Selenium, Playwright, Puppeteer, and Cypress.

Does it change the programming language?

Generally, it tries to keep the language, but if you switch from a system using Java/Python/C# to one using JavaScript/TypeScript (like Playwright), the language might need adjustment.

What if the conversion isn't perfect?

The tool uses detailed reference guides and points out common 'gotchas' to minimize errors. If a specific combination isn't supported, it suggests the closest supported migration.

Details

Original description by the author

Migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#4356
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills