Robot to Playwright Converter

Migrate from Robot Framework to Playwright with Intelligence

Moving a legacy test suite from Robot Framework to Playwright is a massive undertaking. This skill automates the heavy lifting by converting .robot files into idiomatic, high-quality Playwright TypeScript. It doesn't just swap syntax; it understands test intent, preserves BDD structures, and maps complex Robot keywords to web-first Playwright assertions.

What it does

• Converts Robot Framework test cases and keywords into modern Playwright specs.
• Intelligently handles SeleniumLibrary, Browser Library, and RequestsLibrary mappings.
• Detects and preserves original test styles, whether they are BDD (Given/When/Then) or procedural.
• Translates Robot's complex variable syntax and control flows (FOR, IF, WHILE) into clean TypeScript.
• Generates necessary scaffolding including playwright.config.ts and package.json if missing.

Why developers use this skill

Unlike basic search-and-replace scripts, this skill acts like an experienced QA engineer. It prioritizes "web-first" assertions that reduce flakiness and automatically identifies opportunities for Page Object Models. It handles the nuances of the Playwright lifecycle, such as ensuring browser contexts are managed correctly in suite setups, preventing common migration pitfalls like SecurityError in teardowns.

Output format

The result is a set of compilable .spec.ts files. Any custom Python libraries or ambiguous locators that cannot be safely converted are automatically flagged with // TODO comments, allowing you to finalize the migration without losing context.