open-testing-convert-detox

Convert Detox end-to-end tests into target-native scripts for Appium, XCUITest, Espresso, Playwright, and Cypress.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detox end-to-end tests for React Native are tightly coupled to Detox's grey-box runtime. This skill automates converting those tests into runnable equivalents for Appium, XCUITest, Espresso, Playwright, Cypress, and other supported targets, enabling cross-platform automation without re-authoring tests from scratch.

Core Features & Use Cases

  • Detox-to-target decoding: parse Detox tests to extract actions, locators, waits, and assertions.
  • Cross-target emission: map Detox semantics to target-native APIs (Appium, XCUITest, Espresso, Web-based tools).
  • Platform constraint handling: preserve or adapt platform-specific tests and synchronization semantics. Use Case: a RN app currently tested with Detox is migrated to Appium to leverage web-test tooling and broader device coverage.

Quick Start

Provide a complete Detox-to-target conversion plan for an existing Detox e2e suite, generating runnable output for Appium, XCUITest, Espresso, or web-based targets.

Frequently Asked Questions about open-testing-convert-detox

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

FAQPage Schema
How do I convert Detox tests to Appium or Espresso?

Converting Detox tests to Appium or Espresso involves mapping Detox actions, locators, and assertions to target-native APIs. This skill automates the decoding of React Native e2e tests and emits structured canonical steps for cross-platform automation without re-authoring.

Can I migrate React Native e2e tests to Cypress or Playwright?

Yes, you can migrate React Native e2e tests to Cypress or Playwright. The conversion process translates Detox semantics into web-based target APIs, handling locator translation and synchronization so tests run natively on web-based tooling.

What is needed to start converting a Detox e2e suite?

To start converting a Detox e2e suite, you need your existing Detox configuration, specifically the package.json detox entry or a .detoxrc.js file. This provides the necessary context for extracting actions, locators, waits, and assertions.

Does converting Detox tests preserve platform-specific synchronization semantics?

Yes, converting Detox tests preserves platform-specific synchronization semantics. The conversion process explicitly handles platform constraints and adapts synchronization logic to ensure target-native scripts maintain the original test timing and reliability.

What is the best way to translate Detox locators for XCUITest?

The best way to translate Detox locators for XCUITest is through automated locator mapping. This skill decodes Detox test structures and translates grey-box locators into target-native XCUITest identifiers, maintaining element identification integrity.

Are there limitations when migrating Detox tests to other automation frameworks?

Limitations when migrating Detox tests arise from its tightly coupled grey-box runtime. While actions and assertions map to target-native APIs, complex synchronization handling or platform-specific constraints may require manual adaptation for frameworks like Appium or Espresso.