@wdio/browserstack-service 9.33.1 → 9.34.0

package/build/accessibility-handler.d.ts

@@ -10,6 +10,12 @@ declare class _AccessibilityHandler {
     private _browser;
     private isAppAutomate;
     private _framework?;
+    /**
+     * Frameworks whose per-test lifecycle flows through beforeTest/afterTest.
+     * WDIO's jasmine adapter emits the same service hooks as mocha (SDK-7190);
+     * cucumber goes through beforeScenario/afterScenario instead.
+     */
+    private static readonly TEST_HOOK_FRAMEWORKS;
     private _platformA11yMeta;
     private _caps;
     private _suiteFile?;

package/build/bstackLogger.d.ts

@@ -10,6 +10,19 @@ export declare class BStackLogger {
     static debug(message: string, param?: unknown): void;
     static warn(message: string): void;
     static trace(message: string): void;
+    /**
+     * Drain whatever is still sitting in the log stream's buffer onto disk.
+     *
+     * `logToFile` writes to an async `fs.WriteStream`, so a line logged immediately before the
+     * archive is built is very likely NOT in the file yet — the stream's `open` is async too,
+     * so early on the file may not exist at all. Anything that snapshots the log (the debug-log
+     * upload) must flush first or it ships a truncated copy.
+     *
+     * A zero-length write's callback fires only after every chunk queued ahead of it has been
+     * handed to the fs layer, which drains the buffer without ending the stream — unlike
+     * `clearLogger()`, logging continues to work afterwards.
+     */
+    static flushLogFile(timeoutMs?: number): Promise<void>;
     static clearLogger(): void;
     static clearLogFile(): void;
     static ensureLogsFolder(): void;