test-framework-migration-skill
This skill automates the conversion of test automation code across different testing frameworks, helping teams modernize their test suites without manual rewriting. It intelligently maps test logic, assertions, and configurations from one framework to another, reducing migration overhead and maintaining test coverage during infrastructure transitions.
test-framework-migration-skill automates the conversion of your Selenium test scripts to Playwright by intelligently mapping test logic, assertions, and configurations from one framework to another. The skill handles API translation, lifecycle changes, and maintains your test coverage during the migration process, significantly reducing manual rewriting overhead and accelerating your transition to modern testing infrastructure.
AI-generated summary based on this skill's SKILL.md
Install
LambdaTest/agent-skills/test-framework-migration-skill · repository language: Python
git clone https://github.com/LambdaTest/agent-skills
cp -r agent-skills/test-framework-migration-skill ~/.claude/skills/test-framework-migration-skillFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I migrate Selenium tests to Playwright?
test-framework-migration-skill automates the conversion of your Selenium test scripts to Playwright by intelligently mapping test logic, assertions, and configurations from one framework to another. The skill handles API translation, lifecycle changes, and maintains your test coverage during the migration process, significantly reducing manual rewriting overhead and accelerating your transition to modern testing infrastructure.
Can test-framework-migration-skill convert my Selenium WebDriver scripts to Playwright?
Yes, test-framework-migration-skill specializes in converting existing test code across different testing frameworks, including Selenium WebDriver to Playwright. It automatically translates your scripts while preserving test logic and assertions, making it straightforward to port your WebDriver tests without starting from scratch.
What frameworks does test-framework-migration-skill support for conversion?
test-framework-migration-skill supports migration across major testing frameworks including Selenium, Playwright, Cypress, and Puppeteer. Whether you're converting Cypress to Playwright, Puppeteer to Selenium, or any other combination, the skill intelligently maps APIs and lifecycle changes to ensure your test automation infrastructure transitions smoothly.
How does test-framework-migration-skill handle language changes during framework migration?
test-framework-migration-skill can rewrite tests in a different language while simultaneously switching frameworks. For example, it supports converting Selenium Java tests to Playwright TypeScript or refactoring Selenium Python tests to Playwright, automating both the framework conversion and language translation in one process.
What does test-framework-migration-skill do to maintain test coverage during migration?
test-framework-migration-skill preserves your test coverage by automatically mapping test logic, assertions, and configurations from your original framework to the target framework. This intelligent conversion reduces migration overhead and ensures that your test suite maintains its effectiveness and comprehensiveness throughout the infrastructure transition.
Can test-framework-migration-skill help migrate e2e tests between different frameworks?
Yes, test-framework-migration-skill is designed to migrate end-to-end automation from one framework to another by understanding API mappings and lifecycle changes between test frameworks. This capability allows teams to modernize their entire e2e test suites without manual rewriting, making cross-framework test migration straightforward and efficient.
SKILL.md
rendered from the published skill — quoted content, verbatim
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:
|
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 13 files
test-framework-migration-skill/SKILL.md
test-framework-migration-skill/reference/cypress-to-playwright.md
test-framework-migration-skill/reference/cypress-to-selenium.md
test-framework-migration-skill/reference/overview.md
test-framework-migration-skill/reference/playbook.md
test-framework-migration-skill/reference/playwright-to-cypress.md
test-framework-migration-skill/reference/playwright-to-puppeteer.md
test-framework-migration-skill/reference/playwright-to-selenium.md
test-framework-migration-skill/reference/puppeteer-to-playwright.md
test-framework-migration-skill/reference/puppeteer-to-selenium.md
test-framework-migration-skill/reference/selenium-to-cypress.md
test-framework-migration-skill/reference/selenium-to-playwright.md
test-framework-migration-skill/reference/selenium-to-puppeteer.md