Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

playwright-migration

Étoiles1

Forks0

Mis à jour13 mai 2026 à 06:22

Migration skill for moving existing UI automation to Playwright. Use when Codex needs to translate Cypress or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

jovd83

jovd83/playwright-skill

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	playwright-migration
description	Migration skill for moving existing UI automation to Playwright. Use when Codex needs to translate Cypress or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
metadata	{"author":"jovd83","version":"2.0.0","dispatcher-category":"testing","dispatcher-capabilities":"framework-migration, playwright-migration","dispatcher-accepted-intents":"migrate_to_playwright","dispatcher-input-artifacts":"source_test_suite, repo_context, migration_scope","dispatcher-output-artifacts":"migration_plan, migrated_tests, compatibility_notes","dispatcher-stack-tags":"playwright, migration, framework","dispatcher-risk":"high","dispatcher-writes-files":true}

Playwright Migration

Use this skill when the user is moving from another browser automation stack to Playwright.

Migration Workflow

Inventory the existing suite structure, runner assumptions, and shared helpers.
Map framework concepts to the Playwright equivalents.
Choose an incremental migration path that preserves confidence.
Revisit architecture decisions such as fixtures, waiting, locators, and CI once the syntax translation is done.

Guides

Source framework	Guide
Cypress	from-cypress.md
Selenium / WebDriver	from-selenium.md

Output Bias

Prefer migration plans, translated examples, and architecture notes over abstract comparisons.

Plus depuis ce dépôt

même dépôt

playwright-skill

jovd83/playwright-skill

Flagship Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing Playwright. Routes E2E, API, component, visual, accessibility, CI/CD, coverage, docs, CLI automation, and handoff workflows.

2026-05-131

playwright-analysis-requirements

jovd83/playwright-skill

Requirements-analysis skill for Playwright planning and implementation. Use when Codex needs to extract testable behaviors, acceptance criteria, risks, dependencies, or open questions from tickets, specs, markdown docs, or other requirement sources before writing tests or coverage plans.

2026-05-131

playwright-ci

jovd83/playwright-skill

CI and delivery skill for Playwright automation. Use when Codex needs to design, debug, or optimize Playwright execution in GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, sharded pipelines, artifact workflows, or shared setup and teardown.

2026-05-131

playwright-core

jovd83/playwright-skill

Core Playwright implementation skill for resilient test authoring and debugging. Use when Codex needs practical Playwright guidance for locators, assertions, fixtures, authentication, network behavior, API testing, component testing, debugging, framework-specific recipes, or broader test architecture decisions.

2026-05-131

playwright-coverage-matrix-auto-sync

jovd83/playwright-skill

Coverage-maintenance skill for Playwright planning and documentation. Use when Codex needs to synchronize coverage plans, scenario IDs, traceability links, and summary counts after tests, requirements, or narrative test documents change.

2026-05-131

playwright-coverage-plan-generation

jovd83/playwright-skill

Coverage-planning skill for Playwright work. Use when Codex needs to turn confirmed requirements into a structured, risk-aware Playwright coverage plan with scenarios, execution types, priorities, and traceability.

2026-05-131

name	playwright-migration
description	Migration skill for moving existing UI automation to Playwright. Use when Codex needs to translate Cypress or Selenium/WebDriver patterns, plan incremental migration, preserve coverage during framework change, or explain architectural differences that affect the suite design.
metadata	{"author":"jovd83","version":"2.0.0","dispatcher-category":"testing","dispatcher-capabilities":"framework-migration, playwright-migration","dispatcher-accepted-intents":"migrate_to_playwright","dispatcher-input-artifacts":"source_test_suite, repo_context, migration_scope","dispatcher-output-artifacts":"migration_plan, migrated_tests, compatibility_notes","dispatcher-stack-tags":"playwright, migration, framework","dispatcher-risk":"high","dispatcher-writes-files":true}

Playwright Migration

Use this skill when the user is moving from another browser automation stack to Playwright.

Migration Workflow

Inventory the existing suite structure, runner assumptions, and shared helpers.
Map framework concepts to the Playwright equivalents.
Choose an incremental migration path that preserves confidence.
Revisit architecture decisions such as fixtures, waiting, locators, and CI once the syntax translation is done.

Guides

Source framework	Guide
Cypress	from-cypress.md
Selenium / WebDriver	from-selenium.md

Output Bias

Prefer migration plans, translated examples, and architecture notes over abstract comparisons.