Problem

A run started from the dashboard leaves its "Running" state only when the worker streams its final suites, or when the backend broadcasts testStopped. If the spawned process exits before any worker connects, neither arrives. A config preflight that refuses to start, a missing driver, or an unreachable Appium server all do this. The row then shows only a Stop button, so the test cannot be rerun from the dashboard.

Found while rerunning a native Appium example whose server had gone down: the backend log showed the child refusing to start, and the dashboard kept spinning.

Change

• backend (runner.ts): the child's close handler now:
  • reports an exit that happened while the rerun-child flag was still unconsumed, meaning no worker ever connected, through onEarlyExit, with the exit code or signal;
  • clears that flag, so the next unrelated worker is no longer taken for a rerun child;
  • ignores a child that stop() already detached, so a late close of a stopped run no longer clears the run that replaced it.
• backend (index.ts): an early exit broadcasts testStopped with a reason. The Stop route uses the same helper.
• shared: new TestStoppedWsPayload (stopped, timestamp, optional reason) wired into SocketMessage. wire-schema.json and the Python generated types are regenerated.
• app: markRunningAsStopped takes the error message as a parameter. A stopped run still reads "Test execution stopped"; a run that exited early shows its reason, e.g. Run exited before reporting (exit code 1).

Tests

• backend/tests/runner.test.ts: an early exit is reported with its exit code or signal. A run whose worker connected stays silent. A stopped child closing after its replacement started is ignored, and the replacement's own early exit is still reported.
• backend/tests/run-early-exit-broadcast.test.ts: end to end. It spawns a real child that exits with code 3 through POST /api/tests/run, and asserts the testStopped frame a real dashboard client receives.
• app/tests/data-manager.test.ts: a testStopped carrying a reason fails the in-flight test with that message, and the existing stop test now checks the default message.
• All six new tests fail without the source change. pnpm test: 2734 passed. pnpm lint: 0 errors.

Not verified by hand in the dashboard: the stuck state was reproduced before the fix, but the fixed build has only been exercised by the tests above.

🤖 Generated with Claude Code