Test Framework Migration Skill

Organization

LambdaTest

test-framework-migration-skill

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 Selenium, Puppeteer to Playwright, Cypress to Playwright, or vice versa. Triggers on: "migrate", "convert", "port", "selenium to playwright", "playwright to selenium", "puppeteer to playwright", "cypress to playwright", "rewrite tests in", "switch from [framework] to [framework]".

Overview

Publisher	LambdaTest
Repository	`agent-skills`
Skill name	`test-framework-migration-skill`
Stars	377
Forks	74
Bundled files	12
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
12 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by LambdaTest on GitHub. Read the source before you install it.

Installation

Install the Test Framework Migration Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/LambdaTest/agent-skills/tree/main/test-framework-migration-skill
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/LambdaTest/agent-skills.git /tmp/agent-skills
mkdir -p .claude/skills
cp -r /tmp/agent-skills/test-framework-migration-skill .claude/skills/test-framework-migration-skill

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Test Framework Migration Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Test Framework Migration Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Test Framework Migration Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Test Framework Migration Skill

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
Cypress → Selenium	reference/cypress-to-selenium.md

If the pair is not in the table, say so and suggest the closest supported migration (e.g. add WebDriverIO later as a new reference file).

Step 5 — Apply Mappings

Using the reference doc:

Locators — Convert using the API mapping table (e.g. By.id("x") → page.getByRole(...) or page.locator('#x')).
Waits — Convert wait strategy (explicit wait / auto-wait / cy.should).
Actions — Map click, type, select, etc.
Assertions — Map to target's assertion style.
Lifecycle — Adjust setup/teardown (driver vs page, launch vs connect).
Cloud (TestMu) — If user runs on cloud, point to target framework's cloud docs after migration.

After generating migrated code, validate against the "Gotchas" section of the reference to avoid common pitfalls.

Cross-References for Deep Patterns

Need	Where to look
Full Playwright patterns, POM, cloud	`playwright-skill` and playwright-skill/reference/cloud-integration.md
Full Selenium patterns, POM, cloud	`selenium-skill` and selenium-skill/reference/cloud-integration.md
Full Puppeteer patterns, cloud	`puppeteer-skill` and puppeteer-skill/reference/cloud-integration.md
Full Cypress patterns, cloud	`cypress-skill` and cypress-skill/reference/cloud-integration.md
TestMu capabilities (all frameworks)	shared/testmu-cloud-reference.md

Validation Workflow

After generating migrated code:

Ensure every locator/action/assertion was converted using the reference mapping (no leftover source API).
Ensure lifecycle (setup/teardown) matches target framework.
If target is Playwright: use auto-wait assertions (expect(locator).toBeVisible()), not raw waitForTimeout.
If target is Cypress: no async/await with cy commands; use chain style.
If target is Selenium: use explicit WebDriverWait, never Thread.sleep.

Reference Files Summary

File	When to read
reference/overview.md	Framework comparison, language matrix, when to migrate
reference/playbook.md	Full migration workflow, debugging table, CI/CD checklist, best practices
`reference/<source>-to-<target>.md`	Before converting any script for that pair

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Test Framework Migration Skill AI skill do?

Why use Test Framework Migration Skill on TypingMind?

Because you install it once and use it with any model. Test Framework Migration Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Test Framework Migration Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LambdaTest/agent-skills/tree/main/test-framework-migration-skill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Test Framework Migration Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Test Framework Migration Skill?

As many as you like. As long as a model supports skills, you can use Test Framework Migration Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Test Framework Migration Skill AI skill free?

Yes. It is published on GitHub by LambdaTest under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Debugging

openclaw

OrganizationPopular

Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code, including fetching stored…

Openclaw Live Updater

openclaw

OrganizationPopular

Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation. Use for fast-forward update…

Openclaw Pr Maintainer

openclaw

OrganizationPopular

Review, triage, repair, or land OpenClaw issues and pull requests with current-source evidence and the native maintainer workflow.

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Test Framework Migration Skill

Step 1 — Detect Source Framework

Step 2 — Detect Target Framework

Step 3 — Detect Language

Step 4 — Route to Reference

Step 5 — Apply Mappings

Cross-References for Deep Patterns

Validation Workflow

Reference Files Summary

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now