We Want Better
BrowserStack SDK 1.77.0 Brings Cucumber-JUnit 6 to Playwright: QA Upgrade Checks

BrowserStack SDK 1.77.0 Brings Cucumber-JUnit 6 to Playwright: QA Upgrade Checks

October 30, 2026 3 min read

BrowserStack SDK 1.77.0 adds Cucumber-JUnit 6 support for Playwright, ties scenarios to individual Automate sessions, and fixes a TargetClosedError issue. These are the checks QA teams should run before upgrading.


Released on October 15, 2026, BrowserStack SDK 1.77.0 adds a new route for teams running Cucumber, JUnit 6, and Playwright to use BrowserStack's execution and reporting workflow. Playwright projects can now use framework: cucumber-junit6, with each Cucumber scenario linked to its own Automate session. ([browserstack.com](https://www.browserstack.com/docs/sdk/release-notes))

This is more than a minor compatibility change for teams moving from JUnit 5 to JUnit 6 or standardizing on Playwright. The runner, cloud session, reports, and CI result all need to describe the same test outcome. Version 1.77.0 addresses several of those handoffs and fixes a separate Playwright connection problem.

What changed in BrowserStack SDK 1.77.0

The main addition is support for Cucumber on JUnit 6 with Playwright. BrowserStack says the new configuration reports each scenario to Test Reporting & Analytics under the Cucumber-Junit6 framework and gives it a separate Automate session. The reporting system also records whether each scenario passed or failed. ([browserstack.com](https://www.browserstack.com/docs/sdk/release-notes))

Serenity reporting is supported too. That matters to teams using Cucumber feature files alongside Serenity's screenshots, step context, richer reports, or historical analysis. They should need less custom glue between the local runner and BrowserStack dashboards.

There is also a fix for Playwright projects configured with browserstackAutomation: false. Previously, a Playwright connect() call could return TargetClosedError instead of retaining the project's own capabilities. According to the release notes, the SDK now preserves those capabilities when connecting to BrowserStack. ([browserstack.com](https://www.browserstack.com/docs/sdk/release-notes))

Why the JUnit 6 change deserves attention

A JUnit upgrade can expose assumptions that a straightforward local run never shows. Cucumber adapters, lifecycle hooks, parallel execution, reporters, and CI plugins may disagree about test boundaries. The suite can stay green while cloud reporting combines scenarios, drops screenshots, or assigns a browser session to the wrong test.

Linking sessions at scenario level gives investigators a direct route from a failed scenario to its browser session, video, screenshots, logs, and capabilities. That trail matters when a failure appears only on a particular browser, operating system, viewport, or remote configuration.

Upgrade checks for QA teams

  • Verify scenario isolation. Run a feature containing several scenarios. Each one should have the correct Automate session and reporting record.
  • Test both pass and fail outcomes. Deliberately fail one scenario and confirm that the local runner, BrowserStack dashboard, and CI job show the same result.
  • Exercise hooks. Check Before, After, and step hooks, particularly where Serenity reports depend on setup or teardown evidence.
  • Check parallel execution. Run scenarios concurrently and watch for merged sessions, missing screenshots, duplicate test rows, or results assigned to the wrong scenario.
  • Review Playwright capabilities. With browserstackAutomation: false, confirm that browser, viewport, build, and custom capability values survive the connect() call.
  • Compare local and remote runs. A passing local test can still fail in the cloud because of authentication, network access, browser differences, or timing. Include at least one representative remote regression run in the upgrade check.

What this release does not solve

SDK 1.77.0 does not make Cucumber, JUnit, Playwright, Serenity, and CI dependencies compatible by themselves. Nor does it demonstrate that a suite has sufficient coverage. Better session links make failures easier to investigate; they do not replace missing scenarios, strong assertions, or stable test data.

Use the update as a compatibility and observability change, not a waiver for regression testing. Begin with a small, representative set of features. Compare reporting before and after the upgrade, then widen the rollout once scenario ownership and failure evidence match consistently.

For organizations already running Cucumber with Playwright, this release is worth testing now. JUnit 6 support, scenario-level reporting, Serenity compatibility, and the TargetClosedError fix make SDK 1.77.0 a credible upgrade candidate, particularly for pipelines carrying custom test-runner integrations.

Looking for tools to match this read?

Jump into our independent side-by-side comparisons.

Compare Tools