open-testing-convert-playwright-bdd

Convert Playwright-BDD projects into multi-target test framework artifacts.

13|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/AgenticTesting/OpenTestingAI --skill open-testing-convert-playwright-bdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-testing-convert-playwright-bdd
Source: https://github.com/AgenticTesting/OpenTestingAI/tree/main/.opentesting-convert/skills/open-testing-convert-playwright-bdd
Command: npx skills add https://github.com/AgenticTesting/OpenTestingAI --skill open-testing-convert-playwright-bdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides automated conversion and round-trip emission between Playwright-BDD and multi-target test ecosystems, enabling teams to adapt test suites for various runners while preserving provenance.

Core Features & Use Cases

  • Converts Playwright-BDD projects to multiple target ecosystems (Playwright, Cypress, Selenium, Appium, etc.) and supports reverse emission.
  • Preserves features, scenarios, steps, hooks, fixtures, and project metadata to enable accurate cross-target transformations.
  • Facilitates end-to-end workflow interoperability by maintaining source-origin metadata for future round-trips.

Quick Start

Run the converter on a Playwright-BDD project to generate target-specific emission artifacts and preserve round-trip metadata.

Frequently Asked Questions about open-testing-convert-playwright-bdd

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

FAQPage Schema
How do I convert Playwright-BDD test suites to run on other frameworks?

Playwright-BDD conversion translates features, steps, hooks, and fixtures into multi-target artifacts compatible with downstream test runners. It preserves project metadata to enable accurate cross-target transformations and future round-trip emission.

What is round-trip emission for Playwright-BDD projects?

Round-trip emission is the process of converting Playwright-BDD projects into target-specific artifacts and then reversing the flow back to the original source. It preserves source-origin metadata and language configurations for seamless interoperability.

Does converting Playwright-BDD projects preserve hooks and fixtures?

Yes, converting Playwright-BDD projects preserves features, scenarios, steps, hooks, fixtures, and project metadata. This ensures accurate cross-target transformations while maintaining provenance for downstream test frameworks.

Can I use Playwright-BDD automation files with Cypress or Selenium?

Yes, the conversion process transforms Playwright-BDD projects into multi-target artifacts for various test ecosystems including Cypress and Selenium. It applies extraction, mapping, and emission rules to enable cross-target compatibility.

What is the best way to adapt BDD test suites for multiple test runners?

The best way to adapt BDD test suites is using automated conversion that applies extraction and emission rules to features and steps. This generates target-specific artifacts while preserving project metadata for round-trip interoperability.

Are there limitations when converting Playwright-BDD projects across targets?

The conversion requires preserving source-origin metadata and language configurations to maintain round-trip compatibility. If extraction, mapping, and emission rules are not fully satisfied, cross-target transformations may lose provenance or fail.