open-testing-convert-geb

Convert Geb test suites and page objects into Selenium, Playwright, or Cypress code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts Geb test suites and page objects into multi-target automation artifacts, enabling reuse of existing Geb-based test assets across Selenium, Playwright, Cypress, and more.

Core Features & Use Cases

  • Decode Geb's Page objects, Modules, and Content DSLs into target-friendly structures.
  • Emit canonical tests for one feature per test with optional data-driven expansion and environment-aware driver configurations.
  • Support multiple backends (Geb to Selenium, Playwright, Cypress, WebDriverIO, Cucumber, Serenity, and others) from a single codebase.

Quick Start

Provide a Geb project with a GebConfig.groovy and page/spec structure, then run the converter to emit target code.

Frequently Asked Questions about open-testing-convert-geb

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

FAQPage Schema
How do I convert Geb test suites to Selenium or Playwright?

Converting Geb tests to Playwright requires parsing Geb pages, modules, and Spock specs, then emitting framework-specific test code. This Skill automates that translation, supporting targets like Playwright, Selenium, Cypress, and WebDriverIO from a single codebase.

Can I migrate Geb page objects and content DSLs to Cypress?

You can migrate Geb page objects to Cypress by decoding Geb's Page objects, Modules, and Content DSLs into target-friendly structures. The converter preserves page and module relationships when emitting Cypress test code.

What is the process for translating Spock and JUnit-style tests in a Geb project?

Translating Spock and JUnit-style tests involves parsing Geb specs and emitting canonical tests for one feature per test. The converter handles data-driven expansion and environment-aware driver configurations while preserving test logic.

How do I handle environment overrides and driver profiles when migrating from Geb?

When migrating from Geb, the converter extracts frontmatter metadata, driver profiles, and environment overrides from your Geb configuration. This ensures environment-specific settings are preserved in the emitted target framework code.

Does Geb to WebDriverIO conversion preserve modular composition and page relationships?

Yes, Geb to WebDriverIO conversion preserves modular composition. The Skill parses modular composition and maintains page and module relationships, ensuring the emitted WebDriverIO artifacts reflect the original Geb structure.

What are the limitations of converting Groovy Geb tests to Cucumber or Serenity?

Converting Groovy Geb tests to Cucumber or Serenity relies on parsing your GebConfig.groovy and page/spec structure. While it supports these targets, complex Groovy metaprogramming in page objects may require manual adjustments in the emitted artifacts.