Playwright 1.65 Is Out. Check Your Page Objects Before You Bump the Version

Playwright 1.65 Is Out. Check Your Page Objects Before You Bump the Version

ยท 6 min readPublished inEngineering Quality
QAAssist graphic: Playwright 1.65, check your page objects first

Playwright 1.65 adds Bun support, failures-only reports and an exclusive test lock. It also ships ten breaking changes. Here's what can break and a checklist to run first.

Quick answer

Playwright 1.65 was released on November 5, 2026. It can run the test runner under Bun with bunx --bun playwright test, adds a failures reporter and an onlyFailures option, and adds an exclusive test lock. It has ten breaking changes, including page object class fields that read this.page now throwing, actions waiting for elements to be not inert, and stricter cookie matching. It no longer tests on Node.js 20.

Key takeaways

  • Playwright 1.65 was released on November 5, 2026, with Bun support, failures-only reports and an exclusive test lock.
  • The most common break: page object fields that read this.page now throw. Move them into the constructor.
  • Actions now wait for elements to be not inert, so check for the inert attribute if new timeouts appear.
  • Playwright no longer tests on Node.js 20. Use Node 22, 24 or 26.
  • If dashboards read pass counts from reports, keep one full report when you turn on onlyFailures.

Playwright 1.65 came out on November 5, 2026. The headline features are nice: Bun support, a failures-only reporter, and a new exclusive test lock. But the part that will decide whether your Monday goes smoothly is further down the release notes. There are ten breaking changes, and a couple of them hit common test code.

This post covers what is new, what can break, and a short checklist to run before you merge the version bump.

What's new in 1.65

Run tests under Bun. The test runner now works under Bun if you pass the flag:

bunx --bun playwright test

Without --bun, bunx playwright test still runs on Node.js. The release notes list some limits under Bun. There is no watch mode. --tsconfig and JSX options in tsconfig.json have no effect. Stack traces lose async frames, and console output from a test doesn't show up in the trace or UI mode. So this is worth a try on a side branch, not something to switch your main CI to on day one.

Failures-only reports. There is a new failures reporter that prints failures and successful retries as they happen, then a summary, with no progress noise. The HTML, JSON and JUnit reporters also get an onlyFailures option:

export default defineConfig({
  reporter: [
    ['failures'],
    ['html', { onlyFailures: true }],
  ],
});

This is great for big suites where the HTML report is mostly green rows nobody reads. One caution. If a dashboard or script counts passed tests from your JUnit or JSON file, turning on onlyFailures there will make those counts look wrong. Keep one full report for metrics if anything depends on it.

An exclusive lock. You can mark a test so it only runs when nothing else is running:

test('restart the server', { lock: '-exclusive-' }, async () => {
  // No other test runs while this one is running.
});

Everything else keeps running in parallel. This is a cleaner answer for that one test that restarts a service or resets shared data, which teams often handle by moving it to a separate project or a serial file.

Smaller things. test.skip(), test.fixme(), test.fail() and test.slow() now accept just a description. There is a new PLAYWRIGHT_TRANSFORM_CACHE_DIR variable for where transpiled test files go.

The breaking changes most likely to bite

Here are the ones from the release notes that touch everyday test code.

1. Page object class fields

This is the big one. TypeScript class fields now follow useDefineForClassFields, the same as tsc. It is on for ES2022 and later targets, and when no target is set. That breaks a very common page object pattern:

class LoginPage {
  // TypeError: Cannot read properties of undefined (reading 'getByRole')
  readonly submit = this.page.getByRole('button', { name: 'Submit' });

  constructor(private readonly page: Page) {}
}

The field runs before the constructor sets this.page, so it throws. The fix is to move those assignments into the constructor, or set "useDefineForClassFields": false in tsconfig.json. Moving them is the cleaner long term fix.

If your team has dozens of page objects written this way, this change alone can turn a whole suite red in one go. Better to find out on a branch.

2. Actions now wait for elements to be not inert

click(), check(), tap(), fill(), clear() and selectOption() now wait until the element is not inert. If an element, or something around it, has the inert attribute and keeps it, the action times out.

In most apps this is a good change. It stops tests from clicking things a real user can't reach, like a page behind an open modal. But if you see new timeouts after upgrading, check for inert first before you start adding waits.

3. Empty sharded runs now fail

A sharded run fails with "No tests found" if no tests match across all shards. If you run a tag filter in CI that sometimes matches nothing, pass --pass-with-no-tests. An empty single shard still passes if other shards have tests.

browserContext.cookies() and apiRequestContext.cookies() with a URL no longer return host-only cookies for subdomains. A Path=/api cookie no longer matches /apiv2. If you have auth helpers that read cookies by URL, check them.

5. Proxy credentials stay with the proxy

Credentials in the proxy option now only answer proxy challenges. If you were relying on them to log in to a site, use httpCredentials instead.

6. Hidden text leaves accessible names

Text the browser doesn't render, like text inside a closed <details>, is no longer part of accessible names or aria snapshots. That can change getByRole() with a name and any toMatchAriaSnapshot() checks.

The notes list four more: params on API requests now append to the existing query string instead of replacing it, .css style imports in test files must exist, the blob reporter clears its output folder again, and some CommonJS test locations shift by a few columns.

Node and Docker changes

Playwright no longer tests on Node.js 20. Use Node 22, 24 or 26. The official Docker images now ship Node.js 26. If your CI image is pinned to Node 20, update that first, or the upgrade will fail for reasons unrelated to your tests.

Browsers in this release are Chromium 158, Firefox 159 and WebKit 27.2. New browser versions can shift rendering a little, so screenshot tests may need a baseline refresh. Review those diffs before you accept them.

A pre-upgrade checklist

Run this on a branch before merging:

  1. Check Node. Local, CI, and Docker image all on 22 or later.
  2. Bump Playwright and browsers. Update the package and run npx playwright install.
  3. Run tsc --noEmit. Then run the suite once. Look for Cannot read properties of undefined in page objects.
  4. Fix page object fields. Move locator assignments into constructors.
  5. Search for inert in your app if new timeouts appear.
  6. Check sharded CI jobs that can match zero tests. Add --pass-with-no-tests where that is expected.
  7. Review cookie and proxy helpers used for login.
  8. Re-run aria snapshot tests and review any diffs.
  9. Refresh screenshot baselines in the same Docker image your CI uses, and review each change.
  10. Decide on onlyFailures. Turn it on for the HTML report if it helps, but keep a full report wherever metrics come from.

Should you upgrade now?

If your suite is small and your page objects already assign locators in the constructor, the upgrade should be quick. If you have a large suite with the class field pattern everywhere, plan a short focused PR for it rather than mixing it into feature work.

Either way, the safest path is the boring one. Upgrade on a branch, read the failures carefully, and fix the cause instead of adding retries. A version bump is a good moment to clean up the tests that were only passing by luck.

PlaywrightTest AutomationUpgradesBreaking ChangesCI

Frequently asked questions

Playwright 1.65.0 was published on GitHub on November 5, 2026.

About this article

Gulshan KumarProduct & Engineering
Ship release-ready quality

Try QA Assist

Plans, runs, and defect handoff in one workspace.

Get it free