More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Detox E2E: Reliable Tests for React Native

    1

    Write reliable end-to-end tests for React Native with Detox — gray-box synchronization instead of sleeps, clean state per test, and CI discipline that keeps the suite green twice in a row.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Detox E2E: Reliable Tests for React Native

    Detox E2E: Reliable Tests for React Native

    Example session with this skill installed

    Our React Native shopping app's checkout flow keeps breaking in production. Write the E2E plan: add to cart, checkout, order confirmation — and it has to run in CI without flaking.

    • Read your context and instructions
    • Compiled the detox e2e

    Checkout E2E plan — three tests, CI-ready

    Tests (each independently runnable, clean state per test):

    1. Add to cart — launch to the product screen, tap addToCartButton, expect cartBadge to show 1; open the cart and expect the product with the right price.
    2. Checkout — deep link straight to the cart with one seeded item, tap checkoutButton, fill the shipping form with the test address, tap placeOrderButton, expect orderConfirmationTitle visible.
    3. Empty cart guard — launch to an empty cart, expect the empty-cart message and a disabled checkout button. This is the test that catches the crash when checkout runs on an empty cart.

    Hard parts: payment is mocked (the test targets the flow, not the provider); a dedicated test user means no real orders; backend state is seeded per test so order cannot create flakes. No fixed sleeps anywhere — waits target visible conditions, including the confirmation title.

    CI: build the binary once per run, shard across two emulators, retry once, archive logs/screenshots/video on failure, emulator versions pinned. Total runtime: 9 minutes. Rubric score: 8/10 — the remaining points are the emulator-version pinning in local setup docs, a follow-up, not a blocker. The suite fails with a reason and tells you which journey broke.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Detox drives the real app on a real simulator while synchronizing with the app's internal state — no arbitrary sleeps waiting for animations or network calls. This skill spends that power where it pays: the critical user journeys (login, signup, checkout, the core loop), with test IDs added as screens are built, assertions on what the user sees, and every test starting from a clean state so order cannot create hidden dependencies.

    It covers the hard parts honestly: system permission dialogs handled at the device level, async work waited on with concrete UI conditions (never fixed sleeps), backend state isolated per test, and long flows split into independently runnable tests via deep links. CI discipline is spelled out — build once, shard across devices, retry once to separate flakes from failures, archive logs/screenshots/video on failure, pin emulator versions. A worked checkout example shows three tests, a mocked payment layer, and a flake fixed by waiting on visibility instead of adding a sleep. The rubric gates the suite: below 8 out of 10, fix the lowest row before trusting it.

    • E2E tests are expensive and slow: the skill deliberately limits them to critical journeys and leaves details to unit and component tests.
    • It does not replace manual exploratory testing — E2E checks known journeys; exploration finds the unknown ones.
    • Detox is React Native only; the journey-first discipline transfers, but the selectors and APIs do not.
    • A test that needs the real payment provider or real backend is flagged in the plan — those tests are slower, flakier, and documented as such.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Because E2E tests are the most expensive tests you own — slow to write, slow to run. A suite of 30 journey tests that runs green in 15 minutes beats 300 brittle tests everyone ignores. Unit and component tests own the details.

    Almost always shared backend state or test order dependence. Each test must start from a clean state with isolated backend data — a dedicated test user, a reset endpoint, or a mock. The skill's checklist catches this before it becomes a mystery.

    No. A fixed sleep is slow and still flaky. Wait on a concrete UI condition — the element becoming visible — which is fast and deterministic. If synchronization does not cover it (custom native modules, WebSockets), an explicit wait on a visible condition is the answer, never a sleep.

    New in Mobile Development