test(conformance): run the WDIO service through the suite

[vishnuv688]

Stacked on #432 (Nightwatch scenario); base is feat/300-nightwatch-scenario. Part of #300.

What

The WDIO service now runs through the conformance suite in both modes, from packages/conformance/scenarios/wdio/, under its own CLI and attached to the recording backend through the reuse handshake. All four adapters are green, with no new allowlist entries.

What the first runs found

Adapter bugs, fixed here in @wdio/devtools-service (changeset included):

• The config frame was published from beforeSession on a capturer with no socket, so it was dropped every run; only a backend the launcher itself starts, which inherits the path from the environment, ever learned the file. It is now sent from before().
• A failed command's row reached the live socket as error: {}: the raw Error was stored and its message is non-enumerable. The row now carries a serialized error with the browser's own message; webdriver's WebDriverError: <message> when running "<endpoint>" with method "<M>" decoration is stripped, since the other adapters carry the bare message.
• setValue/addValue rows carried the selector only as a leading argument; they now also stamp CommandLog.selector like every other adapter.

Suite assumptions, fixed in packages/conformance:

• The fake browser answers what WebdriverIO routes over BiDi once a session offers it (browsingContext.navigate, browsingContext.getTree, browsingContext.locateNodes, script.callFunction), from the same two-page model as the classic routes.
• run-controls-are-served applies the dashboard's own defaults (silence advertises every control) through resolveRunCapabilities, now in @wdio/devtools-shared with the app delegating to it, and accepts the config frame as what serves them.
• The checker refuses a failed row whose error has no message instead of crashing in the normaliser; a fill's text is read as the trailing argument.

Toolchain

• The scenario runs on the workspace's WebdriverIO 9, the same pins as examples/wdio, with expect-webdriverio declared so pnpm's peer auto-install does not pick a pre-release. A WebdriverIO 10 run cannot coexist in this workspace: @wdio/utils resolves the runner, framework and services from its own location, and both pnpm's hidden hoist and the root node_modules sit on that path, so whichever major is hoisted or declared at the root wins for every project. Moving the repo to 10 is its own change; the wdio-peer job already exercises the service under webdriverio 10.
• A scenario launch may name a working directory, since WebdriverIO's CLI falls back to it when resolving plugins.

Verification

• pnpm build, pnpm lint, pnpm test are green (201 files, 2596 tests), including the conformance suite for all four adapters in both modes and the cross-adapter comparison.
• Regression tests: the config frame (packages/service/tests/index.test.ts), the error on the wire (packages/service/tests/session.test.ts, packages/service/tests/command-error.test.ts), the selector stamp (packages/service/tests/command-selectors.test.ts), the fake's BiDi path (packages/conformance/tests/fakes.test.ts), the rule changes (packages/conformance/tests/checker.test.ts, packages/conformance/tests/agreement.test.ts), shared's resolution (packages/shared/tests/run-capabilities.test.ts).
• Not covered by the scenario: console and network capture, trace zips, per-test slicing, screenshots and assertions.

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge with PR #434’s dependency cleanup.

Summary

Adds the WDIO service to the conformance suite with and without BiDi.

• The conformance suite runs the WDIO service through its own CLI.
• The fake browser models WebdriverIO's BiDi page actions.
• Service command rows keep the browser's errors and selectors.
• The attached dashboard receives the WDIO config file for reruns.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Harness[Conformance harness] --> CLI[WDIO CLI]
  CLI --> Service[Devtools service]
  CLI --> Fake[Fake WebDriver and BiDi browser]
  Service --> Backend[Recording backend]
  Fake --> Truth[Browser actions and documents]
  Backend --> Checker[Rules and adapter comparison]
  Truth --> Checker

Loading

_{Reviews (5) · Last reviewed commit: "chore(conformance): run the WDIO scenari..." · Reviewed by Greptile}