npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

storybook-detox-test-runner

v5.0.0

Published

This project enables you to test your [Storybook for React Native](https://github.com/storybookjs/react-native) stories using [Detox](https://wix.github.io/Detox/).

Readme

Storybook Detox Test Runner

This project enables you to test your Storybook for React Native stories using Detox.

How it works

The test runner injects itself into your Detox tests by overriding the Jest configuration. Before the tests run it generates Jest test files for your Storybook story files. Generated spec files are written into the selected Storybook config directory under .detox-tests, mirroring the relative path of each story file. This avoids filename collisions when multiple stories share the same basename (for example index.stories.tsx).

[!NOTE] The generated Jest test name uses the Storybook story.id to ensure uniqueness across different files (for example multiple Default stories).

Each test uses the Storybook WebSocket channel to render the appropriate story, then runs your story's play function, which may use the Detox API.

Compatibility

  • Storybook 9 and 10 are supported.
  • TypeScript users need TypeScript 5.3 or newer because the public types use resolution-mode import attributes for Storybook ESM types.

Supported story formats

  • CSF3 object stories are supported for Detox tests.
  • CSF Next / factory stories are not supported yet.

Detox test stories should use CSF3 object exports because the generated specs call story.<ExportName>.detox and story.<ExportName>.play. If a story file uses CSF Next / factory stories, the runner stops with an Unsupported CSF Next/factory stories error instead of generating an incorrect spec.

Getting started

  1. Install storybook-detox-test-runner
yarn add -D storybook-detox-test-runner
  1. Configure React Native Storybook

React Native Storybook 9 and 10 use .rnstorybook by default. Existing .storybook directories continue to work, but new React Native Storybook projects should use .rnstorybook.

// .rnstorybook/main.ts
import type { StorybookConfig } from "@storybook/react-native";

const main: StorybookConfig = {
  stories: ["../src/**/*.stories.?(ts|tsx|js|jsx)"],
  deviceAddons: [
    "@storybook/addon-ondevice-controls",
    "@storybook/addon-ondevice-actions",
  ],
};

export default main;
// .rnstorybook/index.ts
import AsyncStorage from "@react-native-async-storage/async-storage";
import { Platform } from "react-native";
import { view } from "./storybook.requires";

const StorybookUIRoot = view.getStorybookUI({
  enableWebsockets: true,
  host: Platform.OS === "android" ? "127.0.0.1" : "localhost",
  port: 7007,
  storage: {
    getItem: AsyncStorage.getItem,
    setItem: AsyncStorage.setItem,
  },
});

export default StorybookUIRoot;

If you change STORYBOOK_WS_PORT, use the same value here.

// metro.config.js
const { getDefaultConfig, mergeConfig } = require("@react-native/metro-config");
const {
  withStorybook,
} = require("@storybook/react-native/metro/withStorybook");

const config = {};

module.exports = withStorybook(
  mergeConfig(getDefaultConfig(__dirname), config),
  {
    configPath: "./.rnstorybook",
  }
);

Do not set websockets: 'auto' in withStorybook for runner tests. That starts React Native Storybook's own channel server, usually on port 7007, while this runner already owns that server.

  1. Install Detox
// .detoxrc.js
/** @type {Detox.DetoxConfig} */
module.exports = {
  extends: 'storybook-detox-test-runner',
  configurations: {
    ...
  • If you use a flag to toggle Storybook, ensure it's enabled during the build, for example:
// .detoxrc.js
  ...
  "app": {
    "type": "android.apk",
    "build": "cd android && STORYBOOK=true ./gradlew assembleRelease assembleAndroidTest -DtestBuildType=release",
    "binaryPath": "android/app/build/outputs/apk/release/app-release.apk"
  }
  ...
  1. Add the generated test directories to your .gitignore
.rnstorybook/.detox-tests
.storybook/.detox-tests

The test runner generates tests in your Storybook config directory, these don't need to be committed to source control.

When STORYBOOK_CONFIG_DIR is not set, the runner looks for .rnstorybook, then .storybook. If neither directory exists, it uses .rnstorybook as the default location. You can force a legacy/custom directory when running tests:

STORYBOOK_CONFIG_DIR=.storybook yarn detox test
  1. Build your test app with yarn detox build

WebSocket mode

The supported mode today is a runner-owned WebSocket channel:

  1. Jest starts the runner WebSocket server on STORYBOOK_WS_PORT, default 7007.
  2. The Storybook UI in the app connects to that server through getStorybookUI({ enableWebsockets: true, host, port }).
  3. Detox tests ask the runner to switch stories over that connection.

React Native Storybook 10 also has withStorybook({ websockets }), but that is a separate channel server mode. If you use it during runner tests, it must not compete with the runner for the same port.

Writing a test

Give your story a play function, access Detox functions like element and by from the detox argument to find and interact with elements.

// counter.stories.tsx
import { type Meta } from "@storybook/react-native";
import type { DetoxStoryObj } from "storybook-detox-test-runner/types";
import Counter from "src/components/counter";

export default {
  component: Counter,
} satisfies Meta<typeof Counter>;

export const WhenIClickOnTheCounterThenTheNumberGoesUp: DetoxStoryObj<
  typeof Counter
> = {
  play: async ({ detox: { by, element, waitFor } }) => {
    // Wait for initial render.
    await waitFor(element(by.text(/Count up/)))
      .toBeVisible()
      .withTimeout(1000);

    // When
    await element(by.text(/Count up/)).tap();
    await element(by.text(/Count up/)).tap();
    await element(by.text(/Count up/)).tap();
    await element(by.text(/Count up/)).tap();
    await element(by.text(/Count up/)).tap();

    // Then
    await waitFor(element(by.text(/5/))).toBeVisible();
  },
};

Running the test

Run Detox as normal with yarn detox test

Per-test configuration

You can trigger advanced behaviour for individual tests by adding a detox property to the story.

// counter.stories.tsx
...

export const WhenIClickOnTheCounterThenTheNumberGoesUp: DetoxStoryObj<typeof Counter> = {
  detox: {
    onlyOnOperatingSystems: ['ios'] // Only run the test on iOS.
    launch: { // Arguments passed to Detox's `device.launchApp`.
      permissions: {
        location: 'inuse'
      }
    }
  },
  play: async ({ detox }) => {
    ...
  }
}

Environment variables

| Variable | Default | Description | | ----------------------------------- | ----------------------------------- | ----------------------------------------------------------------------------------------- | | STORYBOOK_CONFIG_DIR | autodetect, fallback .rnstorybook | Storybook config directory. Generated tests are written to <dir>/.detox-tests. | | STORYBOOK_WS_PORT | 7007 | Runner WebSocket server port. Keep this in sync with getStorybookUI({ port }). | | STORYBOOK_WS_CONNECT_TIMEOUT_MS | 60000 | Timeout (ms) waiting for the app/device to connect. Increase this if app startup is slow. | | STORYBOOK_CHANGE_STORY_TIMEOUT_MS | 20000 | Timeout (ms) waiting for a story to finish rendering after a story switch. | | STORYBOOK_CHANNEL_DEBUG | - | Set to 1 to log WebSocket channel events. |

Troubleshooting

| Problem | Check | | ------- | ----- | | Port 7007 is already in use | Stop the other server, or change both STORYBOOK_WS_PORT and getStorybookUI({ port }). Also check that React Native Storybook is not starting its own channel server through withStorybook({ websockets: 'auto' }). | | Android cannot connect | The runner calls device.reverseTcpPort(STORYBOOK_WS_PORT). Keep the app port equal to STORYBOOK_WS_PORT; 127.0.0.1 is usually the right Android host for Detox. | | Wrong config directory | RN Storybook 9+ defaults to .rnstorybook. Use STORYBOOK_CONFIG_DIR=.storybook only for legacy/custom projects. | | Unsupported CSF Next/factory stories | Convert Detox-tested stories to CSF3 object stories. CSF Next / factory stories are not supported by the runner yet. |