integration-setup-failed-error
The distinct error thrown in a test worker when that project’s integration global setup already failed in the main process.
Without it a worker whose setup failed gets no transport options at all, and silently rebuilds the owned desktop CDP default — so an Android project’s suite would run on desktop, and then die on Failed to parse URL from /json (an owned instance nobody launched has no CDP endpoint). Every file in the project reported that mask while the real cause appeared once, far above, in the setup log. This error replaces the mask: it is raised before any transport is constructed, and it carries the original setup failure verbatim, so each report names the actual cause.
It deliberately carries no stack trace: the failure happened in the global setup, which already logged its own trace, and a second trace pointing into the harness only suggests the harness broke.
Classes
Section titled “Classes”| Class | Description |
|---|---|
| IntegrationSetupFailedError | Thrown when a test worker asks for the ambient transport of a project whose global setup failed. Carries the configured transport, the original error’s name, and its message, so callers can instanceof-match and report the real cause instead of a downstream transport error. |
Interfaces
Section titled “Interfaces”| Interface | Description |
|---|---|
| IntegrationSetupFailedErrorConstructorParams | Parameters for the IntegrationSetupFailedError constructor. This is also the shape the framework adapter publishes to its workers (Vitest: provide('setupError')). |