研究检索操作浏览器github未标认证来源可访问许可证需确认审计通过

test-framework-migration-skill（测试框架迁移技能）

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据，避免为了通过测试而改坏真实逻辑；涉及浏览器或外部服务时，应区分本地模拟、测试环境和生产环境。

总安装

768

周安装

GitHub Stars

246

下载量

256

CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：test-framework-migration-skill（测试框架迁移技能）
来源仓库：https://github.com/lambdatest/agent-skills
仓库路径：skills/test-framework-migration-skill
安装命令：
npx skills add https://github.com/lambdatest/agent-skills --skill test-framework-migration-skill
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

skills.shnpx skills

npx skills add https://github.com/lambdatest/agent-skills --skill test-framework-migration-skill

简介

用于辅助测试设计、自动化测试、用例整理和回归验证。

适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。
使用时需要确认项目测试框架、运行命令和夹具数据，避免为了通过测试而改坏真实逻辑。
涉及浏览器或外部服务时，应区分本地模拟、测试环境和生产环境。
安装方式：github，需通过 npx skills add 命令从指定仓库添加。

SKILL.md

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/<source>-to-<target>.md`	Before converting any script for that pair

适合场景

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.63%

按下载量换算96

Claude

30.67%

按下载量换算79

Cursor

19.99%

按下载量换算51

Gemini CLI

9.32%

按下载量换算24

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力，使用时可能读取或操作网页内容，需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/lambdatest/agent-skills

SKILL.md 来源

github.com

/lambdatest/agent-skills/tree/main/skills/test-framework-migration-skill

skills-sh

skills.sh

/lambdatest/agent-skills/test-framework-migration-skill

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

test-for-wang（测试王）

下一个 Skill

test-frontend-units（测试前端单元）

用于辅助前端页面、组件、样式和交互逻辑的开发与维护。它适合让 Agent 生成或审查 React、Next.js、Vue、Tailwind、CSS 等相关代码，整理组件结构，或定位布局和性能问题。使用时需要结合项目现有设计系统、路由和构建方式，避免只生成孤立片段；涉及页面改动时，应配合本地预览和构建检查确认视觉效果。