chore(deps-dev): bump @wdio/browserstack-service from 9.29.1 to 9.32.1

[dependabot]

Bumps @wdio/browserstack-service from 9.29.1 to 9.32.1.

Release notes

Sourced from @​wdio/browserstack-service's releases.

@​wdio/browserstack-service@​9.32.1

Patch Changes

• aefd604: - Fixed a statically-skipped test (it.skip) being left orphaned as "in progress" on the Test Observability dashboard in the CLI flow. Such tests are reported from the un-awaited onTestSkip reporter hook, so their TestRunFinished event could still be pending when the worker tore down; the after() hook now drains these skip reports before the session closes so the test is correctly reported as skipped.

• 1a973e9: - fix: Accessibility command wrapping.

• a24973b: - Fixed Test Observability not being fully disabled for a run when the build could not be started (e.g. an unsupported framework) — such sessions no longer emit observability events or get linked to a non-existent build.

• 8539e5f: fix(a11y): restore per-command auto-scanning for App Automate accessibility sessions

  App Automate accessibility sessions were skipped by the per-command overwriteCommand wrapping in onBeforeExecute (guarded to !isAppAccessibility), so app a11y scans only fired via an explicit performScan() or the end-of-test lifecycle scan — per-command auto-scanning that web sessions get was effectively disabled for app. Command wrapping now applies to app sessions too, with each overwriteCommand call individually guarded so a command the appium driver does not register is skipped (logged at debug) instead of aborting onBeforeExecute. Commands appium does register (click, setValue, ...) now auto-scan on App Automate, matching the web flow.

@​wdio/browserstack-service@​9.32.0

Minor Changes

• 9b80e47: Add a skipAppOverride service option for App Automate (Appium) runs. With skipAppOverride: true the service classifies the session as App Automate even when no app option is set, does not upload an app, and does not inject an appium:app capability — the user supplies the app reference themselves (e.g. a pre-uploaded bs:// hash as a driver capability or via BROWSERSTACK_APP_ID). Setting it together with an app option logs a conflict warning and ignores the app option; skipAppOverride: false with no app fails fast with a configuration error before any session starts. Unset keeps existing behaviour unchanged.

@​wdio/browserstack-service@​9.31.0

Minor Changes

• bebf0f1: - App Accessibility scans triggered inside test hooks (before/after, beforeEach/afterEach) are now correctly attributed to the wrapping test instead of being dropped.

• 517d64d: - Custom tags (browser.setCustomTags) set inside Mocha beforeEach / afterEach hooks now reliably land on the intended test's custom metadata, unioning and deduping with tags set in the test body (parity with Java @Before / @After).

• 05fe529: Custom tags (browser.setCustomTags) set inside Mocha beforeEach / afterEach hooks now reliably land on the intended test's custom metadata. WDIO's Mocha runner fires user hooks outside the SDK's per-test tracking span — beforeEach runs before the test instance is tracked and afterEach runs after it is finished — so tags set in those hooks previously either attached to the wrong test or were dropped from the payload.

  Tags set in beforeEach are now buffered and flushed onto the test at its start, and the test-finished event is deferred past the afterEach window so late tags still make the payload. Values set across beforeEach, the test body, and afterEach union and dedupe onto the test (parity with Java @Before / @After).

@​wdio/browserstack-service@​9.30.2

Patch Changes

• a43e534: - Fixed skipped tests (it.skip, this.skip() in before/beforeEach hooks) and suites aborted by a failed before hook not being reported to Test Observability when using the CLI.
  • Fixed Automate sessions from skipped/aborted spec files not being linked to the Test Observability build.

@​wdio/browserstack-service@​9.30.1

Patch Changes

• de1684b: Refresh the framework session id on reloadSession so Test Observability keeps linking to the correct session after a reload (#54), and declare browser.setCustomTags on the WebdriverIO.Browser type so it type-checks in consumer projects (SDK-6882, #53).

@​wdio/browserstack-service@​9.30.0

Minor Changes

• e4cf295: Publish from the standalone browserstack/wdio-browserstack-service repo, at parity with the WebdriverIO monorepo. Includes Load Testing Service (LTS) support, one-to-many Test-Case-ID tagging (setCustomTestCaseId), correct test/hook finish on mocha timeouts, per-batch failure isolation in the request queue, accessibility Browser type augmentations, and yauzl upgraded to ^3.4.0. No user-facing API change.
• 46ee119: BrowserStack now publishes @wdio/browserstack-service from its own repository (browserstack/wdio-browserstack-service) on an independent release cadence, using npm OIDC trusted publishing. No change for end users — same package name and the same services: ['browserstack'] configuration continue to work unchanged.

... (truncated)

Changelog

Sourced from @​wdio/browserstack-service's changelog.

9.32.1

Patch Changes

• aefd604: - Fixed a statically-skipped test (it.skip) being left orphaned as "in progress" on the Test Observability dashboard in the CLI flow. Such tests are reported from the un-awaited onTestSkip reporter hook, so their TestRunFinished event could still be pending when the worker tore down; the after() hook now drains these skip reports before the session closes so the test is correctly reported as skipped.

• 1a973e9: - fix: Accessibility command wrapping.

• a24973b: - Fixed Test Observability not being fully disabled for a run when the build could not be started (e.g. an unsupported framework) — such sessions no longer emit observability events or get linked to a non-existent build.

• 8539e5f: fix(a11y): restore per-command auto-scanning for App Automate accessibility sessions

  App Automate accessibility sessions were skipped by the per-command overwriteCommand wrapping in onBeforeExecute (guarded to !isAppAccessibility), so app a11y scans only fired via an explicit performScan() or the end-of-test lifecycle scan — per-command auto-scanning that web sessions get was effectively disabled for app. Command wrapping now applies to app sessions too, with each overwriteCommand call individually guarded so a command the appium driver does not register is skipped (logged at debug) instead of aborting onBeforeExecute. Commands appium does register (click, setValue, ...) now auto-scan on App Automate, matching the web flow.

9.32.0

Minor Changes

• 9b80e47: Add a skipAppOverride service option for App Automate (Appium) runs. With skipAppOverride: true the service classifies the session as App Automate even when no app option is set, does not upload an app, and does not inject an appium:app capability — the user supplies the app reference themselves (e.g. a pre-uploaded bs:// hash as a driver capability or via BROWSERSTACK_APP_ID). Setting it together with an app option logs a conflict warning and ignores the app option; skipAppOverride: false with no app fails fast with a configuration error before any session starts. Unset keeps existing behaviour unchanged.

9.31.0

Minor Changes

• bebf0f1: - App Accessibility scans triggered inside test hooks (before/after, beforeEach/afterEach) are now correctly attributed to the wrapping test instead of being dropped.

• 517d64d: - Custom tags (browser.setCustomTags) set inside Mocha beforeEach / afterEach hooks now reliably land on the intended test's custom metadata, unioning and deduping with tags set in the test body (parity with Java @Before / @After).

• 05fe529: Custom tags (browser.setCustomTags) set inside Mocha beforeEach / afterEach hooks now reliably land on the intended test's custom metadata. WDIO's Mocha runner fires user hooks outside the SDK's per-test tracking span — beforeEach runs before the test instance is tracked and afterEach runs after it is finished — so tags set in those hooks previously either attached to the wrong test or were dropped from the payload.

  Tags set in beforeEach are now buffered and flushed onto the test at its start, and the test-finished event is deferred past the afterEach window so late tags still make the payload. Values set across beforeEach, the test body, and afterEach union and dedupe onto the test (parity with Java @Before / @After).

9.30.2

Patch Changes

• a43e534: - Fixed skipped tests (it.skip, this.skip() in before/beforeEach hooks) and suites aborted by a failed before hook not being reported to Test Observability when using the CLI.
  • Fixed Automate sessions from skipped/aborted spec files not being linked to the Test Observability build.

9.30.1

Patch Changes

• de1684b: Refresh the framework session id on reloadSession so Test Observability keeps linking to the correct session after a reload (#54), and declare browser.setCustomTags on the WebdriverIO.Browser type so it type-checks in consumer projects (SDK-6882, #53).

9.30.0

Minor Changes

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: a7f4df1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR