Playwright 1.65: Bun Support, Failure-Only Reports and What to Check Before Upgrading

Playwright 1.65.0, released November 5, 2026, introduces opt-in support for running the test runner under Bun, a failure-focused terminal reporter, and an `onlyFailures` setting for HTML, JSON, and JUnit reports, while discontinuing tested support for Node.js 20 in favor of Node 22, 24, or 26. The release includes 10 breaking changes, notably TypeScript page-object class fields that access `this.page` before constructor initialization, actions that now wait for non-inert elements, altered cookie and API request behavior, stricter handling of empty sharded runs, and blob reporters clearing their output directories. Bun execution offers faster alternative transpilation but lacks or changes several Node-based capabilities, including watch mode, tsconfig support, custom ESM loaders, detailed async stacks, trace console capture, and dependency-aware `--only-changed` behavior. Failure-only reports can reduce human-facing artifact clutter but also omit successful tests from totals, so unfiltered machine-readable reports should remain the source for dashboards and quality gates. The recommended upgrade process is to run TypeScript checks for TS2729 errors, update CI images and Node versions, run suites in the matching Playwright 1.65 Docker image, classify failures, regenerate and review visual baselines separately, preserve full blob reports when sharding, and account for several known early-release bugs involving decorators, JSON string bodies, and virtual clock intervals.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.