protractor-playwright-migrator

Migrate Creatio end-to-end tests from Protractor to Playwright with TestKit compliance.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RoukSonix/claude-code-octopus --skill protractor-playwright-migrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protractor-playwright-migrator
Source: https://github.com/RoukSonix/claude-code-octopus/tree/main/.opencode/skills/protractor-playwright-migrator
Command: npx skills add https://github.com/RoukSonix/claude-code-octopus --skill protractor-playwright-migrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of migrating end-to-end tests from the legacy Protractor framework to the modern Playwright framework, ensuring business logic preservation and TestKit compliance.

Core Features & Use Cases

  • Automated Migration Planning: Generates a detailed migration plan, including gap analysis and phased implementation steps.
  • TestKit-First Migration: Ensures adherence to Playwright TestKit conventions for pages, elements, and fixtures.
  • Business Logic Preservation: Analyzes and preserves critical business logic and assertions during the migration.
  • Verification & Debugging: Integrates with mcp chrome-devtools for live application verification and Playwright artifacts for debugging.
  • Use Case: Migrate a suite of 500 Protractor end-to-end tests for a complex web application to Playwright, minimizing manual effort and ensuring test suite stability and maintainability.

Quick Start

Use the protractor-playwright-migrator skill to create a migration plan for Protractor tests located in './e2e/protractor' to Playwright tests in './e2e/playwright'.

Frequently Asked Questions about protractor-playwright-migrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Protractor end-to-end tests to Playwright?

Migrating Protractor tests to Playwright involves analyzing existing test locations, mapping them to Playwright-compliant structures, preserving business logic, and generating a phased migration plan with gap analysis for missing components.

What is the best way to convert a large Protractor test suite to Playwright?

Converting a large Protractor suite to Playwright is best handled by automating reconnaissance and planning, mapping pages and elements to TestKit conventions, and verifying migrated tests using browser debugging tools and Playwright artifacts.

Does migrating Protractor tests to Playwright preserve existing business logic and assertions?

Yes, migrating Protractor tests to Playwright preserves critical business logic and assertions by analyzing existing test structures before mapping them to Playwright TestKit-compliant pages, elements, and fixtures.

Can I verify migrated Playwright tests during the conversion process?

Yes, you can verify migrated Playwright tests during conversion by integrating with chrome-devtools for live application verification and leveraging Playwright artifacts for debugging any failing assertions.

How do I handle missing TestKit components when moving from Protractor to Playwright?

Handling missing TestKit components during Protractor to Playwright migration requires performing a gap analysis against target TestKit conventions, then optionally implementing the identified pages, elements, and fixtures in phased steps.