SDK-7772 WDIO Jasmine v9 platformisation

[AdityaHirapara]

What is this about?

Moves WebdriverIO + Jasmine (v9) from the legacy in-SDK flow onto the CLI/binary flow, at functional parity with legacy jasmine. Products: Test Observability, web Accessibility, Automate / App Automate session marking, and Percy. Legacy stays as the runtime fallback (binary unavailable, multiremote). Paired binary PR: browserstack/browserstack-binary#1837, which must be released first.

Jasmine on the CLI flow

• jasmine is added to CLISupportedFrameworks, with a new WdioJasmineTestFramework.
• Jasmine has two event sources, as legacy did. The WDIO reporter (not awaited) is the only site that sees pending, fit-excluded and beforeAll-failed specs, plus beforeAll/afterAll with their suite. The awaited service hooks are the only points with a live driver at each spec's start and end.
  • Both sources call trackEvent (the reporter with source: 'reporter').
  • Reporter events: the instance and uuid are minted synchronously, then sent to TestHub through an ordered queue.
  • Service events wait for the queued reporter events, reuse the same instance (matched by fullName), and reach Accessibility, Automate and Percy through the dispatcher with skipTestHub. TestHubModule ignores those events.
  • The reporter's isSynchronised drains the queue before the worker exits.
• Automate: the session name is the describe chain, and sessionNameFormat, sessionNameOmitTestTitle and sessionNamePrependTopLevelSuiteTitle behave as on legacy. The session verdict is legacy service.after()'s rule, computed in AutomateModule from the inputs service.after(result) already tracks, and only the live session is marked (a reloaded one keeps its onReload mark).
• Accessibility: the per-test gate uses the spec description. There is no pre-test scan window for jasmine, and hooks never gate, as on legacy.
• Percy: testcase-mode snapshot names come from the spec title, as on legacy.

Shared CLI changes (all WDIO frameworks)

• Command capture moved to TestHubModule. The WebDriver command/result listeners are registered once per browser at driver creation, instead of in service.before() and insights-handler. Each framework class decides which test or hook a log belongs to. The legacy path is untouched.
  • HTTP command logs are now reported on the CLI flow for mocha and cucumber too (previously only screenshots were). Mocha hook command logs go to their hook run, as on legacy.
• Per-test Test: … annotation now comes from AutomateModule for mocha and jasmine, never cucumber. This restores mocha's annotation, which the CLI flow had dropped.
• Test Plan ID: a CLI-arg --browserstack.testManagementOptions.testPlanId <id> is now sent as the id. Previously the binary received true from the space-separated form. Config and env variants are unchanged.
• sessionNamePrependTopLevelSuiteTitle / sessionNameOmitTestTitle are kept out of capabilities.

Verification

• Unit: 60 files / 1473 tests.
• Jasmine vs legacy 9.39.0, local, on BrowserStack:
  • CP-1 Test Observability: test tree, hooks, results, 238/238 HTTP logs on the right specs.
  • CP-2 session marking: default, ignoreHooksStatus, setSessionStatus:false / setSessionName:false, reload, beforeAll failure.
  • Accessibility modes; Percy auto/click/testcase/manual; App Automate.
  • Fallback, multiremote and release-mode (obfuscated) binary.
• BStackAutomation wdio_jasmine v9: wrapper_default, test_plan_id, nppp, session_marking_failed, percy_a11y_default, android/ios default.
• Mocha and cucumber no-regression runs, plus their HTTP-log parity against pre-CLI legacy (mocha 9.20.1, cucumber 9.36.2).

Known issues (existing before this PR; tickets to follow)

• A per-capability bstack:options.buildTag is dropped by the binary on the CLI flow, for every WDIO framework.
• BrowserStack Local started through a proxy can hang on the CLI flow (no timeout on Local start in the binary).
• Cucumber command logs inside Before/After hooks attach to the hook run; legacy attached them to the scenario.

Related Jira task/s

• https://browserstack.atlassian.net/browse/SDK-7772 (epic https://browserstack.atlassian.net/browse/SDK-7053)

Release (mandatory for every PR — required for the ready-for-review label)

Version bump: (required — tick exactly one)

• minor (backwards-compatible feature)
• patch (bug fix or other small change)

Release notes type: (optional)

• New Feature
• Bug Fix
• Other Improvement

Release notes (customer-facing): (optional but encouraged)

• WebdriverIO with Jasmine (v9) now runs on the BrowserStack CLI: Test Observability, Accessibility, Automate/App Automate session status and naming, and Percy.
• HTTP command logs now appear in Test Observability for WebdriverIO Mocha and Cucumber, and Mocha sessions show a per-test annotation again.
• Fixed --browserstack.testManagementOptions.testPlanId <id> passed on the command line not reaching Test Management.

Release notes (internal): (required — engineer-facing; what actually changed / why)

• Added WdioJasmineTestFramework and enabled jasmine in CLISupportedFrameworks. The reporter feeds TestHub through an ordered queue; awaited service hooks feed the Accessibility, Automate and Percy modules with skipTestHub.
• Moved the jasmine session verdict into AutomateModule; service.after() passes legacy verdict inputs for jasmine only.
• Moved WebDriver command/result capture from service.ts / insights-handler.ts into TestHubModule, with framework-class attribution. Enabled HTTP command logs for mocha and cucumber.
• Moved the per-test annotation into AutomateModule (mocha + jasmine); skip reports are not annotated.
• stripTestPlanIdArg removes the CLI-arg test plan id before forwarding argv to the binary. getBinConfig resolves it through getTestPlanId.
• Requires the binary release from browserstack-binary#1837 (WebdriverIO-jasmine module and TestHub allow-list).

Checklist

• Ready to review
• Has it been tested locally?

PR Validations

Run Tests: Comment RUN_TESTS to trigger sanity tests.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Central YAML (base), Organization UI (inherited), Workspace UI (inherited)
• Review profile: ASSERTIVE
• Plan: Enterprise
• Run ID: 163682af-8a31-4a6a-adbb-f1fdae062f26

---

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}