open-testing-convert-karate

name	open-testing-convert-karate
description	Convert Karate (JVM API + UI testing DSL) suites — `.feature` files using Karate's Gherkin-superset DSL with built-in HTTP / UI primitives (no step definitions), `karate-config.js`, `karate.callonce` / `karate.call` feature reuse, `background` blocks, `* def` variables, `Given url / When method / Then status / And match` verbs, `match` deep-equal/contains/regex/schema, `configure` directives, JSON/XML/YAML/GraphQL payloads, `read()` fixtures, parallel JUnit 5 runner, UI layer (`driver`, `click`, `input`, `waitFor`, `screenshot`), embedded JS/Java via `Java.type()`, Scenario Outline with `Examples`, Maven/Gradle wiring. Targets: Selenium, Playwright, Cypress, Cucumber, Appium, Eggplant, OpenTest.AI, Testers.AI. MANDATORY TRIGGERS: "convert Karate", "Karate to <target>", "karate.call", "karate-config", "Given url", "And match".
license	MIT
metadata	{"family":"open-testing-convert","source":"karate","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","webdriverio","puppeteer","appium","cucumber","eggplant","testcafe","nightwatch","codeceptjs","taiko","protractor","katalon","playwright-bdd","behave","specflow","behat","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — Karate

Converts Karate (JVM API + UI testing DSL) suites to any supported target, and emits Karate from any source.

Karate is unusual among BDD tools: it has no step-definitions layer. The .feature file itself is the test code — Karate provides a fixed DSL vocabulary (Given url, When method, Then match, And def, etc.) that interprets Gherkin directly. This means extraction reads meaning straight from the feature file without cross-referencing step definition classes.

When to use

Trigger when:

• com.intuit.karate:karate-junit5 / karate-junit4 / karate-apache / karate-core as Maven/Gradle dependencies.
• karate-config.js in src/test/java or src/test/resources.
• .feature files using Karate's DSL verbs: Given url, Given path, When method POST, Then status 200, Then match response == {...}, And def var = ..., * def ..., configure, call, callonce, read(...).
• logback-test.xml at test resources root (Karate's logging convention).
• karate.options system property set in build config.
• Test runner classes containing @Karate.Test annotations (JUnit 5) or Runner.runFeature(...) patterns.

How to use

1. Read the master orchestrator first.
2. Read this skill's reference files: source-profile.md, extraction.md, mappings.md.
3. Read target primer for your target.
4. Emit per target Emission Checklist.

Scope

• Karate 1.0+ (including 1.4+ with improved UI support) and Karate 0.9.x legacy.
• Feature files with Karate DSL — API-heavy tests (dominant use case) and UI tests (Karate UI).
• karate-config.js environment-based configuration.
• configure directives: configure headers, configure cookies, configure ssl, configure retry, configure connectTimeout, configure readTimeout, configure logPrettyRequest, configure logPrettyResponse, configure proxy.
• karate.call / karate.callonce / call / callonce feature composition.
• match operator with deep-equal, contains, schema markers (#string, #number, #boolean, ##string nullable, #regex, #uuid, #ignore, #present, #notnull, #array, #object, #null, #notpresent).
• match each for array-element assertions.
• match contains / match contains only / match contains any / match contains deep variants.
• assert for boolean expressions.
• JSON / XML / YAML / GraphQL / form-encoded / multipart payloads.
• read('classpath:...') / read('file:...') / read('./relative') fixture loading.
• Embedded JavaScript: * def x = function() { return 42; } and function invocation * def y = x().
• Java interop: * def List = Java.type('java.util.ArrayList').
• Scenario Outlines with Examples: tables; dynamic Examples via pipe syntax.
• UI testing subset: driver <url>, click, input, waitFor, waitForText, screenshot, submit, retry, script, optional, highlight, scroll.
• Parallel runner with JUnit 5 @Karate.Test + Karate.Builder.
• karate.tags tag filtering via CLI or runner.
• signal() / listen() for async-test orchestration.
• karate.jsonPath(), karate.xmlPath(), karate.lowerCase(), many built-in utility functions.

Out of scope

• Karate Gatling performance testing (different runtime) — flag; preserve metadata only.
• Karate Robot (desktop automation) — flag; handle per-case.
• Custom Java HttpClient injection via configure httpClientClass — preserve as todo with warning.
• karate.env variants that change test semantics dynamically at runtime in ways not resolvable at extraction time — extract the default env and record others as env_profiles.

Quick reference

Karate	Canonical	Example target
Given url 'https://example.com/api'	{kind: "http_request_setup", base_url: "https://example.com/api"}	RestAssured baseURI / Requests session
Given path '/users', userId	{kind: "http_path", segments: ["/users", "userId"]}	path joining on target
When method GET	completes pending {kind: "http_request", method: "GET", ...}	requests.get(url)
Then status 200	{kind: "assert", assertion_kind: "http_status_equals", value: 200}	resp.status_code == 200
And match response == {id: 1}	{kind: "assert", assertion_kind: "http_body_deep_equal", expected: {...}}	assert resp.json() == {...}
And match response.items[*].name == '#string'	{kind: "assert", assertion_kind: "jsonpath_match_schema", path, schema: "#string"}	target-specific schema helper
* def user = read('classpath:users/alice.json')	{kind: "fixture_load", name: "user", path, format: "json"}	fixture inlined
* call read('create-user.feature') { name: 'Alice' }	{kind: "call_feature", ref, args}	reusable helper function
Given driver 'https://example.com'	{kind: "navigate", url} (UI mode)	Playwright page.goto
And input('#email', '[e-mail]')	{kind: "input", locator, value}

See reference/mappings.md for full cookbook.