limrun-detox-testing

Limrun Detox

Use this for Detox runtime work on Limrun iOS. Keep build concerns separate unless the user explicitly asks for a native build.

Components

• Tester: local Node/Jest/Detox process.
• Mediator: detox run-server, usually local to the agent machine.
• App client: injected by limulator through lim ios launch-app --runtime detox.

CLI Flow

Check current help before running commands you have not used in this session:

lim ios tunnel --help
lim ios launch-app --help

Run the long-lived mediator, tester, and tunnel from separate terminals. Before using this quick path, ensure the project's .detoxrc reads the session environment. Detox does not consume these variables automatically:

session: {
  server: process.env.DETOX_SERVER || 'ws://localhost:8099',
  sessionId: process.env.DETOX_SESSION_ID || 'limrun-detox',
}

The complete configuration appears under Detox Test Setup below.

Terminal 1:

npx detox run-server -p 8099 -l verbose

Terminal 2:

lim ios tunnel \
  --selector localhost:8099 \
  --detach \
  --id <ios-id>
DETOX_SERVER_URL="ws://localhost:8099"

Terminal 3 starts the tester before the app connects:

DETOX_SERVER="ws://localhost:8099" \
DETOX_SESSION_ID=<session-id> \
  npx detox test --no-start

Then relaunch the app from Terminal 2. --detox-version is optional when running from the project with node_modules/detox.

lim ios launch-app <bundle-id> \
  --id <ios-id> \
  --runtime detox \
  --detox-server-url "$DETOX_SERVER_URL" \
  --detox-session-id <session-id> \
  --detox-version <detox-version>

Prefer starting the tester before the app connects, or use the maintained orchestration in limrun-inc/typescript-sdk examples/detox-ios, to avoid benign mediator "cannot forward" noise. If you manually launch the app before npx detox test --no-start, that mediator message is expected until the tester connects.