@wdio/browserstack-service 9.34.1 → 9.35.1

package/build/service.d.ts

@@ -43,6 +43,13 @@ export default class BrowserstackService implements Services.ServiceInstance {
     private _percyCaptureMode;
     private _percyHandler?;
     private _turboScale;
+    /**
+     * Only mocha's own bail drops the rest of a spec. wdio's top-level `bail` is a launcher
+     * spec-scheduling filter (it stops queueing further specs once N runners have failed) and
+     * never reaches mocha, so under it every test in the current spec still runs — enumerating
+     * on it would report tests as skipped that are about to execute.
+     */
+    private _mochaBail;
     constructor(options: BrowserstackConfig & Options.Testrunner, _caps: Capabilities.ResolvedTestrunnerCapabilities, _config: Options.Testrunner);
     _updateCaps(fn: (caps: WebdriverIO.Capabilities) => void): void;
     beforeSession(config: Omit<Options.Testrunner, 'capabilities'>, capabilities: WebdriverIO.Capabilities): Promise<void>;
@@ -59,6 +66,28 @@ export default class BrowserstackService implements Services.ServiceInstance {
     afterHook(test: Frameworks.Test | CucumberHook, context: unknown, result: Frameworks.TestResult): Promise<void>;
     beforeTest(test: Frameworks.Test): Promise<void>;
     afterTest(originalTest: Frameworks.Test, context: never, results: Frameworks.TestResult): Promise<void>;
+    /**
+     * Whether this failure will be retried, in which case mocha has not dropped anything yet and
+     * the tests after it are still going to run.
+     *
+     * `results.retries` only tracks wdio's spec-file retries — `@wdio/utils` builds it as
+     * `{ attempts: 0, limit: repeatTest }` and `@wdio/mocha-framework` never feeds `mochaOpts.retries`
+     * into it, so under mocha-level retries it stays `{0, 0}` and tells us nothing. Read mocha's own
+     * runnable state for that case, otherwise the cascade fires on the first attempt and reports
+     * tests as skipped that the retry then actually runs.
+     */
+    private hasRetryPending;
+    /**
+     * mocha's `bail` aborts the run on the first failure, so every test the spec had not reached
+     * yet is dropped without emitting any event and never appears on the dashboard. Report them
+     * as skipped — same cascade the failed-hook path uses, from the spec's root suite so sibling
+     * describes are covered too (bail kills the whole spec, not just the failing describe).
+     *
+     * The root can span more than one file when specs are grouped — `MochaAdapter` adds every spec
+     * it is handed to one mocha instance. Cascading across them is still correct: bail aborts that
+     * whole runner, so those tests do not run either.
+     */
+    private reportBailSkippedTests;
     after(result: number): Promise<void>;
     /**
      * For CucumberJS
@@ -72,6 +101,23 @@ export default class BrowserstackService implements Services.ServiceInstance {
     afterScenario(world: ITestCaseHookParameter): Promise<void>;
     beforeStep(step: Frameworks.PickleStep, scenario: Pickle): Promise<void>;
     afterStep(step: Frameworks.PickleStep, scenario: Pickle, result: Frameworks.PickleResult): Promise<void>;
+    /**
+     * Whether accessibility is being driven by the binary rather than the classic handler.
+     *
+     * Precisely: it decides whether the CLASSIC handler owns the session's accessibility state.
+     * It is the same condition that gates `AccessibilityHandler.before()` in the `before` hook, so
+     * keeping it in one place is what stops the two drifting.
+     *
+     * The two paths are not strictly exclusive. `AccessibilityModule` is registered on
+     * `startBinResponse.accessibility?.success` alone, independent of provider — `isNonBstackA11y`
+     * exists for exactly the turboscale / non-BrowserStack case — so with the binary up against a
+     * non-BrowserStack provider the module can hold real state AND the handler's `before()` will
+     * have run. Both then need migrating, which is what the caller does.
+     *
+     * `isRunning()` alone is NOT equivalent, and that is the trap: under a non-BrowserStack
+     * provider it is true while the classic handler is the one holding the live state.
+     */
+    private _isCliAccessibilityFlow;
     onReload(oldSessionId: string, newSessionId: string): Promise<void>;
     _isAppAutomate(): boolean;
     _updateJob(requestBody: unknown): Promise<unknown>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wdio/browserstack-service",
-  "version": "9.34.1",
+  "version": "9.35.1",
   "description": "WebdriverIO service for better Browserstack integration",
   "author": "BrowserStack <support@browserstack.com>",
   "homepage": "https://github.com/browserstack/wdio-browserstack-service",
@@ -55,7 +55,7 @@
   "dependencies": {
     "@browserstack/ai-sdk-node": "1.5.17",
     "@bufbuild/protobuf": "^2.5.2",
-    "@grpc/grpc-js": "1.13.3",
+    "@grpc/grpc-js": "~1.13.5",
     "@percy/appium-app": "^2.0.9",
     "@percy/selenium-webdriver": "^2.2.2",
     "@types/gitconfiglocal": "^2.0.1",