@wdio/browserstack-service 9.39.3 → 9.39.5

package/build/cli/modules/automateModule.d.ts

@@ -5,6 +5,7 @@ export default class AutomateModule extends BaseModule {
     logger: typeof BStackLogger;
     browserStackConfig: Options.Testrunner;
     private sessionMap;
+    private mochaTestsRan;
     static readonly MODULE_NAME = "AutomateModule";
     /**
      * Create a new AutomateModule
@@ -25,11 +26,17 @@ export default class AutomateModule extends BaseModule {
      * `after()` marked the session failed; that whole accumulation is gated
      * `setSessionStatus && !BrowserstackCLI.isRunning()`, so it is dead while the binary is up.
      *
-     * Cucumber-gated deliberately. `wdio_mocha` has the identical latent shape on this flow, but
-     * legacy mocha behaved the same way, so repairing it here would be an unrequested behaviour
-     * change to the one framework already working on the CLI flow.
+     * Cucumber only — mocha hooks go through onMochaHookEnd.
      */
     onBuildLevelHookEnd(hookKey: string, args: Record<string, unknown>): Promise<void>;
+    /**
+     * A failed mocha hook produces no test result — the tests it aborts are reported skipped,
+     * which counts as passed — so the session was marked PASSED even though the run failed.
+     * Legacy fails the session on any hook error unless ignoreHooksStatus is set and a test ran;
+     * `mochaTestsRan` is only final at teardown, so the verdict is decided in onAfterExecute.
+     */
+    onMochaHookEnd(hookKey: string, args: Record<string, unknown>): Promise<void>;
+    private isMochaInstance;
     private isCucumberInstance;
     /** The hook's reported name (`BEFORE_ALL for <feature>`), so the session reason names the hook. */
     private resolveHookName;