Generate Test Automation Code Across 15+ Frameworks

This skill migrates and converts test automation scripts between Selenium, Playwright, Puppeteer, and Cypress by applying API mappings, lifecycle changes, and pattern conversions from a set of reference docs, acting as a senior QA automation architect. It works in five steps: detect the source framework from message text or open-file signals (e.g. driver.findElement/By.id for Selenium, page.getByRole/@playwright/test for Playwright, page.$/puppeteer.launch for Puppeteer, cy.get/cy.visit for Cypress - asking explicitly if ambiguous); detect the target framework from phrasing like "to Playwright" or "to Cypress" (asking if only the source was named); detect the implied language change, since a Selenium-in-Java/Python/C# to Playwright migration usually means rewriting to TypeScript/JavaScript while Playwright/Puppeteer/Cypress conversions typically stay in JS/TS; route to the exact matching reference file for that source-target pair (ten documented pairs: Selenium↔Playwright, Selenium↔Puppeteer, Selenium↔Cypress, Puppeteer↔Playwright, Playwright↔Cypress), always reading it before generating any migrated code, and flagging an undocumented pair rather than guessing; and apply the mappings themselves - locators via the API mapping table, wait strategy conversion (explicit wait vs auto-wait vs cy.should), action mapping (click/type/select), assertion style mapping, lifecycle adjustment (driver vs page, launch vs connect), and a pointer to the target framework's cloud docs if the user runs on LambdaTest's TestMu cloud. After generating migrated code, it validates against the reference's "Gotchas" section and a five-point checklist: no leftover source-framework API calls, lifecycle matches the target framework, Playwright targets use auto-wait assertions like expect(locator).toBeVisible() rather than waitForTimeout, Cypress targets avoid async/await with cy commands in favor of chaining, and Selenium targets use WebDriverWait rather than Thread.sleep. It cross-references dedicated per-framework skills (playwright-skill, selenium-skill, puppeteer-skill, cypress-skill) for deeper Page Object Model and cloud-integration patterns beyond the migration itself, plus a shared TestMu cloud capabilities reference.

Use it whenever a user asks to migrate, convert, or port tests from one of Selenium/Playwright/Puppeteer/Cypress to another, or asks to rewrite tests in a different framework. Always read the exact source-to-target reference file before generating any converted code - never improvise a mapping from general framework knowledge. Do NOT attempt a migration pair that isn't in the documented reference table without saying so explicitly and suggesting the closest supported alternative - guessing at an undocumented conversion risks silently wrong API mappings.

Inputs: the existing test script(s) or open files, the named or inferred source framework, and the target framework the user wants to migrate to. Outputs: migrated test code with locators, waits, actions, assertions, and lifecycle setup/teardown converted per the matching reference mapping, validated against that reference's gotchas and the target-framework-specific checklist (auto-wait assertions for Playwright, chained syntax for Cypress, WebDriverWait for Selenium).

Routes to ten documented source-target reference files covering every pairwise combination of Selenium, Playwright, Puppeteer, and Cypress, plus an overview reference for the framework/language comparison matrix and a playbook reference for the full migration workflow and CI/CD checklist. Cross-references companion per-framework skills (playwright-skill, selenium-skill, puppeteer-skill, cypress-skill) and a shared TestMu cloud-capabilities reference for LambdaTest cloud runs.

QA engineers and test automation teams migrating an existing test suite from one browser-automation framework to another who need accurate, gotcha-checked API and lifecycle conversions rather than a naive line-by-line rewrite.