[🐛 Bug]: Tauri service clobbers user's command overrides for `click` etc

[gpaciga]

Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Which service/package is affected?

Tauri Service (@wdio/tauri-service)

Package Version

v1.1.0

Node.js Version

v24.12.0

Operating System

macOS

What happened?

With CrabNebula driver, I was able to define an override for the click command to enforce a wait:

  before: () => {
    browser.overwriteCommand(
      "click",
      async function (
        this: WebdriverIO.Element,
        origClick: (options?: Partial<ClickOptions> | undefined) => Promise<void>,
        options?: Partial<ClickOptions> & { timeout?: number },
      ) {
        const { timeout, ...clickOpts } = options ?? {};
        await this.waitForClickable({ timeout });
        await origClick(clickOpts);
      },
      true, // element-scoped override
    );
  },

However, with tauri-service, it seems like this override doesn't take effect. It looks like tauri-service calls installCommandOverrides in its before(), but this runs after the user's before hook and undoes any customization.

Expected Behavior

I should be able to add customizations to these commands, so in my override,

        await this.waitForClickable({ timeout });
        await origClick(clickOpts); // this should call the tauri-service version of click

Minimal Reproducible Example

in wdio.conf.js:

  before: () => {
    browser.overwriteCommand(
      "click",
      async function (
        this: WebdriverIO.Element,
        origClick: (options?: Partial<ClickOptions> | undefined) => Promise<void>,
        options?: Partial<ClickOptions> & { timeout?: number },
      ) {
        console.log("User's click override used");
        await origClick(clickOpts);
      },
      true, // element-scoped override
    );
  },

Relevant Log Output

Additional Context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

[goosewobbler]

Investigated and reproduced. Two findings:

1. Root cause is deeper than hook ordering

WDIO stores element-scoped overrides (overwriteCommand(name, fn, /* attachToElement */ true)) in a map keyed by command name — they do not chain. In @wdio/utils's overwriteCommand, the attachToElement path just does __elementOverrides__.value[name] = customCommand; only the browser-scoped path captures and chains origCommand. So a second overwriteCommand('click', …, true) overwrites the first in that slot — last writer wins.

The service's before() runs after the user's, so the service's override replaces the user's. It's symmetric: if the user's hook ran last, the service's mock-sync override would be the one silently dropped instead. Two element-scoped overrides of the same command simply can't coexist via this API. This is platform-independent (pure JS), not macOS-specific.

2. Also affects @wdio/electron-service

Identical mechanism — installCommandOverrides() → overrideElementCommand() → browser.overwriteCommand(commandName, testOverride, true) for ['click', 'doubleClick', 'setValue', 'clearValue']:

• Electron: packages/electron-service/src/service.ts:567-597
• Tauri: packages/tauri-service/src/service.ts:513-536

@wdio/electrobun-service and @wdio/dioxus-service are not affected — they assign their API directly (installApi) and never wrap element commands.

Suggested fix (both services)

Drop the overwriteCommand wrappers and trigger the mock refresh from the afterCommand worker hook instead — call the mock-update path (updateAllMocks() / the mock-update scheduler) when commandName ∈ {click, doubleClick, setValue, clearValue}. The wrappers only run the original command and then refresh mocks (they never modify args or the return value), so afterCommand is a behavior-preserving drop-in that never touches the user's command chain. The Tauri service already has a sibling beforeCommand hook firing for these commands, so the plumbing is proven.

[goosewobbler]

Scoping update: the Tauri half is fixed in #434 (moves mock-sync to the afterCommand hook so user command overrides are no longer clobbered).

The Electron half — same root cause, identical installCommandOverrides pattern — is split out to #432, since its fix is materially larger (it interacts with the #292 batched MockUpdateScheduler + multiremote per-instance routing, and ~44 test refs). This issue now tracks Tauri only; scope:electron removed accordingly.