open-testing-convert-serenity

Convert Serenity BDD projects into a canonical multi-target representation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts Serenity BDD test suites into a unified, multi-target emission surface, enabling teams to reuse existing test logic across Selenium, Playwright, Cypress, Appium, and other runtimes while preserving patterns like Screenplay and Lean Page Objects.

Core Features & Use Cases

  • Detect Serenity projects and extract runners, drivers, narratives, and requirement structures.
  • Decode Screenplay tasks, interactions, questions, and page objects into a canonical, target-agnostic representation.
  • Emit emission-ready metadata for downstream targets, including data-driven tests and Cucumber integration.

Quick Start

Run the converter on your Serenity project root and choose the emission target to generate the canonical output.

Frequently Asked Questions about open-testing-convert-serenity

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

FAQPage Schema
How do I convert Serenity BDD tests to run with Playwright or Cypress?

You can convert Serenity BDD tests by running the converter on your project root to extract runners, drivers, and narratives into a canonical representation. This emission-ready output can then target multiple test runtimes like Selenium, Playwright, and Cypress.

What is a canonical representation for Serenity Screenplay tests?

A canonical representation is a target-agnostic format that decodes Serenity Screenplay tasks, interactions, and questions. It captures runner types, driver profiles, and test metadata, allowing teams to reuse existing test logic across multiple downstream runtimes.

Does the converter support both Java and JavaScript Serenity projects?

Yes, the converter supports both Java and JavaScript Serenity BDD project variants. It applies to Serenity configurations, Screenplay tasks, Lean Page Objects, standard Page Objects, Serenity REST, Cucumber suites, and data-driven tests to extract narratives and requirement hierarchies.

How do I handle unresolved Cucumber glue or custom Interactions during conversion?

The converter routes extraction through a configurable flow and surfaces warnings for unresolved glue or custom Interactions. This alerts you to specific custom logic that requires manual mapping before generating the emission-ready output for your downstream targets.

Can I extract data-driven tests and Serenity REST configurations for migration?

Yes, you can extract data-driven tests and Serenity REST configurations for migration. The converter captures object locators, driver profiles, and test metadata, decoding these elements into the canonical representation for downstream emission to new test runners.