open-testing-convert-xcuitest

Convert XCUITest UI test suites into multi-platform automation artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts XCUITest UI test suites into cross-target automation artifacts so teams can reuse existing UI tests across multiple platforms without rewriting tests.

Core Features & Use Cases

  • Converts Apple's XCUITest UI tests (Swift/Objective-C) to compatible targets such as Appium, Detox, Selenium/WebDriverIO, Playwright, Cypress, Nightwatch, CodeceptJS, Katalon, OpenTest.AI, testers.ai, and other automation runners.
  • Supports multi-app contexts, UI interruption monitors, page objects, performance measurements, and test plan configurations for scalable migration.
  • Use Case: Migrate a large iOS app's UI suite to a cross-platform test harness while preserving element selectors, wait semantics, and launch configurations.

Quick Start

Consult the master orchestrator and reference files, then emit per-target artifacts following the emission checklist.

Frequently Asked Questions about open-testing-convert-xcuitest

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

FAQPage Schema
How do I convert XCUITest UI tests to Appium or Playwright?

XCUITest UI tests are converted to Appium or Playwright by extracting test steps, page objects, and launch configurations, then mapping XCUIElement queries to canonical steps for cross-platform emission.

What is the best way to migrate iOS UI tests to a cross-platform test harness?

Migrating iOS UI tests to a cross-platform harness involves converting XCUITest suites into multi-target automation artifacts, preserving element selectors, wait semantics, and launch configurations for scalable migration.

Can I convert Swift XCUITest suites to run multi-app scenarios in Detox?

Yes, converting Swift XCUITest suites to Detox supports multi-app contexts and UI interruption monitors, allowing teams to reuse existing iOS UI tests across multiple platforms without rewriting tests.

Does XCUITest conversion work with CodeceptJS and Katalon?

Yes, XCUITest conversion works with CodeceptJS and Katalon, applying extraction semantics for test steps and page objects to emit compatible automation artifacts for these and other runners.

How do I extract page objects from XCUITest for Selenium WebDriverIO?

Extracting page objects from XCUITest for Selenium WebDriverIO involves applying extraction semantics to test plans and mapping XCUIElement queries to canonical steps for cross-platform emission.

What are the limitations of converting XCUITest to cross-platform automation?

Converting XCUITest to cross-platform automation requires iOS projects with UI test targets and frontmatter configurations including language, platform, bundle_id, and test plans, restricting it to properly structured XCUITest suites.