open-testing-convert-behave

Convert Behave Python BDD test suites into Selenium, Playwright, and Cypress equivalents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Behave projects often require costly porting when adapting to new automation ecosystems. This skill automates the translation of Gherkin features, Python step definitions, and environment hooks into multiple target runtimes, reducing duplication and drift.

Core Features & Use Cases

  • Automates canonicalization of Behave features, backgrounds, scenarios, and scenario outlines with expanded examples for multiple targets.
  • Generates target glue code (step definitions and driver hooks) for Selenium, Playwright, Cypress, WebDriverIO, and more, preserving tags and hooks metadata.
  • Supports environment.py hooks, fixtures, userdata, and custom types while producing auditable, reproducible results across backends.

Quick Start

Provide your Behave project to the converter and run it to output target-ready tests and glue code.

Frequently Asked Questions about open-testing-convert-behave

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

FAQPage Schema
How do I convert Behave tests to Playwright or Cypress?

Converting Behave tests to Playwright or Cypress is automated by canonicalizing Gherkin features and Python step definitions into target-ready glue code. The process preserves tags, hooks, fixtures, and userdata mappings across backends.

What is a canonical representation for Behave BDD tests?

A canonical representation for Behave BDD tests is a stable intermediate format capturing steps, hooks, fixtures, userdata mappings, and tag or rule metadata. It enables safe, auditable translations across multiple automation targets like Selenium and Playwright.

Can I migrate environment.py hooks and fixtures to WebDriverIO?

Yes, you can migrate environment.py hooks and fixtures to WebDriverIO. The conversion supports environment.py hooks, fixtures, userdata, and custom types, producing reproducible glue code across backends.

Does the Behave conversion tool support scenario outlines with expanded examples?

Yes, Behave conversion supports scenario outlines with expanded examples. It canonicalizes backgrounds, scenarios, and outlines, generating canonical tests per scenario or per expanded outline for each target runtime.

What is the best way to port a Python BDD test suite to Selenium?

The best way to port a Python BDD test suite to Selenium is to automate the translation of Behave features and step definitions. This generates target glue code from a stable canonical representation, reducing duplication and drift.

When should I not use automated Behave test conversion?

You should not use automated Behave test conversion when your project lacks the standard features directory, environment.py, and steps structure. The converter requires these canonical Behave project components to produce auditable translations.