Run any Skill in Manus with one click

open-testing-convert-webdriverio

Stars13

Forks1

UpdatedApril 20, 2026 at 11:58

Convert WebDriverIO test suites (`browser.*`, `$()`/`$$()` element queries, `waitForDisplayed`, WebdriverIO's shorthand selector prefixes like `~`, `android=`, `-ios predicate string:`) to and from Selenium, Playwright, Cypress, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles WDIO Mocha/Jasmine/Cucumber specs, sync (v6) and async (v7+) APIs, mobile and desktop configurations, wdio.conf.js services, and shared hooks. Use whenever the user wants to migrate a WebDriverIO suite, port WDIO tests to another framework, or round-trip WDIO through OpenTest.AI. MANDATORY TRIGGERS — "convert WebDriverIO", "WebDriverIO to <target>", "WDIO to Playwright", "WDIO to Cypress", "wdio.conf.js", "migrate WDIO", any mention of WebDriverIO alongside any supported target.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

AgenticTesting

AgenticTesting/OpenTestingAI

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

4 files

SKILL.md

readonly

name	open-testing-convert-webdriverio
description	Convert WebDriverIO test suites (`browser.*`, `$()`/`$$()` element queries, `waitForDisplayed`, WebdriverIO's shorthand selector prefixes like `~`, `android=`, `-ios predicate string:`) to and from Selenium, Playwright, Cypress, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles WDIO Mocha/Jasmine/Cucumber specs, sync (v6) and async (v7+) APIs, mobile and desktop configurations, wdio.conf.js services, and shared hooks. Use whenever the user wants to migrate a WebDriverIO suite, port WDIO tests to another framework, or round-trip WDIO through OpenTest.AI. MANDATORY TRIGGERS — "convert WebDriverIO", "WebDriverIO to <target>", "WDIO to Playwright", "WDIO to Cypress", "wdio.conf.js", "migrate WDIO", any mention of WebDriverIO alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"webdriverio","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","appium","cucumber","eggplant","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — WebDriverIO

Converts WebDriverIO test suites to any supported target, and emits WebDriverIO from any source. Defers orchestration to open-testing-convert.

When to use

Trigger when:

The user references WebDriverIO, wdio.conf.js/wdio.conf.ts, browser.url(...), $(...)/$$(...), ~accessibilityId, android=new UiSelector(), -ios predicate string:..., or @wdio/cli.
The user uploads a spec file with describe/it/before/after plus await browser... or synchronous browser... calls.
package.json contains @wdio/* packages.
Mobile-flavour WDIO with capabilities: { platformName: "Android" }.

How to use

Read the master orchestrator first. ../open-testing-convert/SKILL.md.
Determine runtime flavour. WDIO 6 (sync Fiber-based) vs WDIO 7+ (async/await). Forward-convert from sync to async as an intermediate step — all code targets use async; the sync flavour only survives when emitting WDIO 6 back.
Detect backend. Web (Chromedriver/Geckodriver) vs Mobile (Appium) vs Desktop (Winium, etc.). Mobile WDIO routes through the same extraction as raw Appium; web routes through Selenium-like extraction.
Read target primer for your target (same catalogue as Selenium/Playwright/Cypress skills).
Read this skill's reference files:
- reference/source-profile.md — WDIO API surface, selector prefixes, config structure, services.
- reference/extraction.md — command → canonical intent.
- reference/mappings.md — per-target cookbook.
Read shared references as needed.
Emit per target Emission Checklist. Preamble lists: WDIO version detected, sync vs async, backend (web/mobile), services used (e.g., wdio-sauce-service), selector strategy distribution.

Scope

Mocha, Jasmine, and Cucumber runners (Cucumber paths delegate to open-testing-convert-cucumber for the feature-file layer).
Sync (WDIO 6) and async (WDIO 7+) APIs.
Web (standalone) and Mobile (Appium-backed) modes.
WDIO custom commands (browser.addCommand).
WDIO services (chromedriver, sauce, visual, shared-store).
Page object pattern (WDIO's common POM style with getter-based selectors).
Shared spec hooks via wdio.conf.js (beforeTest, afterSuite, etc.).

Out of scope

WDIO with Cucumber features — the feature file itself is handled by open-testing-convert-cucumber; the step-defs are in scope here.
Pure Appium raw code (no WDIO) — use open-testing-convert-appium.
Old WDIO 4/5 without TypeScript/async patterns — preserved as a legacy fallback mode.

Quick reference

WDIO call	Canonical	Code target
`browser.url('/x')`	`{kind: "navigate", url: "/x"}`	`page.goto`/`driver.get`/`cy.visit`
`$('#email').setValue('x')`	`{kind: "input", locator: {strategy: "css", value: "#email"}, value: "x"}`	framework-specific input
`$('~Sign in').click()`	`{kind: "click", locator: {strategy: "accessibility_id", value: "Sign in"}}`	`AppiumBy.accessibilityId` / `getByRole` on web
`$('android=new UiSelector().text("X")').click()`	`{kind: "click", locator: {strategy: "android_uiautomator", value: "new UiSelector().text(\"X\")"}}`	`AppiumBy.androidUIAutomator`
`$('-ios predicate string:label == "X"').click()`	`{kind: "click", locator: {strategy: "ios_predicate", value: "label == \"X\""}}`	`AppiumBy.iOSNsPredicateString`
`expect(elem).toBeDisplayed()`	`{kind: "assert", assertion_kind: "element_visible", locator}`	framework-specific
`browser.waitUntil(() => ...)`	`{kind: "wait_for", wait_kind: "custom_condition"}`	framework-specific

See reference/mappings.md for full cookbook.

More from this repository

same repository

open-testing-coverage

AgenticTesting/OpenTestingAI

Test coverage analysis, gap detection, coverage reporting, and coverage optimization using the COVERED agent pipeline. Use this skill whenever the user mentions test coverage, coverage analysis, coverage gaps, traceability matrix, coverage heat map, coverage dashboard, coverage metrics, coverage trends, test intensity, risk-based coverage, requirement coverage, code coverage mapping, or wants to know if their testing is sufficient. Also trigger when users ask about uncovered requirements, orphaned tests, coverage regression, or coverage targets. MANDATORY TRIGGERS: coverage, traceability, gap analysis, RTM, heat map, coverage dashboard, coverage trend, test intensity evaluation.

2026-05-1413

open-testing-create

AgenticTesting/OpenTestingAI

Generate concrete test cases, test data, and test scripts from a test design technique and context. Applies 106 test design techniques (boundary value analysis, equivalence partitioning, decision tables, state transitions, pairwise, combinatorial, etc.) to enumerate test conditions and author realistic test cases with inputs, expected results, and traceability. Use this skill whenever the user needs to: create test cases from a technique, apply a testing method to requirements, generate test data, design test scenarios, or populate test scripts. Triggers include: 'test cases', 'create tests', 'test design', 'apply [technique name]', 'generate test data', 'test scenarios', or any technique name (BVA, EP, combinatorial, etc.).technique name (BVA, EP, combinatorial, etc.).

2026-05-1413

open-testing-design

AgenticTesting/OpenTestingAI

Generate comprehensive test strategies, quality engineering approaches, risk analysis, and optimal technique selection. Use this when you need to develop test strategies, perform quality risk analysis, select test design techniques, assess testability, estimate test effort, define governance structures, or establish test exit criteria and coverage targets.

2026-05-1413

open-testing-management

AgenticTesting/OpenTestingAI

Test management, defect management, process evaluation, and maturity assessment using the MANAGES agent pipeline. Use this skill whenever the user mentions test management, defect management, process improvement, TMMi, maturity assessment, ARCI matrix, quality policy, test policy, process evaluation, defect lifecycle, triage, test process, roles and responsibilities, QAM, QPM, GTA, generic test agreements, process maturity, test improvement, or wants to evaluate and improve their testing practices. Also trigger for defect tracking, anomaly management, process compliance, test governance, or organizational testing capability. MANDATORY TRIGGERS: test management, defect management, TMMi, maturity, ARCI, process improvement, quality policy, defect lifecycle, process evaluation, test governance.

2026-05-1413

open-testing-plan

AgenticTesting/OpenTestingAI

Generate comprehensive test plans, schedules, resource allocation, environment setup, and test data strategies. Use this when you need to develop master test plans, level-specific test plans, allocate resources and environments, plan non-functional testing, define end-to-end testing chains, or establish test data management strategies.

2026-05-1413

open-testing-reporting

AgenticTesting/OpenTestingAI

Test reporting, progress dashboards, release advice, and final test reports using the REPORTS agent pipeline. Use this skill whenever the user mentions test report, progress report, test dashboard, release advice, go/no-go decision, test metrics, defect trends, test execution summary, quality assessment, final test report, lessons learned, RAG status, or wants to generate any kind of testing status or quality report. Also trigger for executive summaries, sprint test reports, release readiness, or stakeholder communication about testing. MANDATORY TRIGGERS: test report, progress, dashboard, release advice, go/no-go, test metrics, defect trend, RAG status, quality report, test summary

2026-05-1413

name	open-testing-convert-webdriverio
description	Convert WebDriverIO test suites (`browser.*`, `$()`/`$$()` element queries, `waitForDisplayed`, WebdriverIO's shorthand selector prefixes like `~`, `android=`, `-ios predicate string:`) to and from Selenium, Playwright, Cypress, Appium, Cucumber, Eggplant (SenseTalk), OpenTest.AI, Testers.AI Recorder, and Testers.AI Dynamic. Handles WDIO Mocha/Jasmine/Cucumber specs, sync (v6) and async (v7+) APIs, mobile and desktop configurations, wdio.conf.js services, and shared hooks. Use whenever the user wants to migrate a WebDriverIO suite, port WDIO tests to another framework, or round-trip WDIO through OpenTest.AI. MANDATORY TRIGGERS — "convert WebDriverIO", "WebDriverIO to <target>", "WDIO to Playwright", "WDIO to Cypress", "wdio.conf.js", "migrate WDIO", any mention of WebDriverIO alongside any supported target.
license	MIT
metadata	{"family":"open-testing-convert","source":"webdriverio","orchestrator":"open-testing-convert","targets":["selenium","playwright","cypress","appium","cucumber","eggplant","opentestai","testersai-recorder","testersai-dynamic"]}

Convert — WebDriverIO

Converts WebDriverIO test suites to any supported target, and emits WebDriverIO from any source. Defers orchestration to open-testing-convert.

When to use

Trigger when:

The user references WebDriverIO, wdio.conf.js/wdio.conf.ts, browser.url(...), $(...)/$$(...), ~accessibilityId, android=new UiSelector(), -ios predicate string:..., or @wdio/cli.
The user uploads a spec file with describe/it/before/after plus await browser... or synchronous browser... calls.
package.json contains @wdio/* packages.
Mobile-flavour WDIO with capabilities: { platformName: "Android" }.

How to use

Read the master orchestrator first. ../open-testing-convert/SKILL.md.
Determine runtime flavour. WDIO 6 (sync Fiber-based) vs WDIO 7+ (async/await). Forward-convert from sync to async as an intermediate step — all code targets use async; the sync flavour only survives when emitting WDIO 6 back.
Detect backend. Web (Chromedriver/Geckodriver) vs Mobile (Appium) vs Desktop (Winium, etc.). Mobile WDIO routes through the same extraction as raw Appium; web routes through Selenium-like extraction.
Read target primer for your target (same catalogue as Selenium/Playwright/Cypress skills).
Read this skill's reference files:
- reference/source-profile.md — WDIO API surface, selector prefixes, config structure, services.
- reference/extraction.md — command → canonical intent.
- reference/mappings.md — per-target cookbook.
Read shared references as needed.
Emit per target Emission Checklist. Preamble lists: WDIO version detected, sync vs async, backend (web/mobile), services used (e.g., wdio-sauce-service), selector strategy distribution.

Scope

Mocha, Jasmine, and Cucumber runners (Cucumber paths delegate to open-testing-convert-cucumber for the feature-file layer).
Sync (WDIO 6) and async (WDIO 7+) APIs.
Web (standalone) and Mobile (Appium-backed) modes.
WDIO custom commands (browser.addCommand).
WDIO services (chromedriver, sauce, visual, shared-store).
Page object pattern (WDIO's common POM style with getter-based selectors).
Shared spec hooks via wdio.conf.js (beforeTest, afterSuite, etc.).

Out of scope

WDIO with Cucumber features — the feature file itself is handled by open-testing-convert-cucumber; the step-defs are in scope here.
Pure Appium raw code (no WDIO) — use open-testing-convert-appium.
Old WDIO 4/5 without TypeScript/async patterns — preserved as a legacy fallback mode.

Quick reference

WDIO call	Canonical	Code target
`browser.url('/x')`	`{kind: "navigate", url: "/x"}`	`page.goto`/`driver.get`/`cy.visit`
`$('#email').setValue('x')`	`{kind: "input", locator: {strategy: "css", value: "#email"}, value: "x"}`	framework-specific input
`$('~Sign in').click()`	`{kind: "click", locator: {strategy: "accessibility_id", value: "Sign in"}}`	`AppiumBy.accessibilityId` / `getByRole` on web
`$('android=new UiSelector().text("X")').click()`	`{kind: "click", locator: {strategy: "android_uiautomator", value: "new UiSelector().text(\"X\")"}}`	`AppiumBy.androidUIAutomator`
`$('-ios predicate string:label == "X"').click()`	`{kind: "click", locator: {strategy: "ios_predicate", value: "label == \"X\""}}`	`AppiumBy.iOSNsPredicateString`
`expect(elem).toBeDisplayed()`	`{kind: "assert", assertion_kind: "element_visible", locator}`	framework-specific
`browser.waitUntil(() => ...)`	`{kind: "wait_for", wait_kind: "custom_condition"}`	framework-specific

See reference/mappings.md for full cookbook.