What's New in Playwright 1.63? Test Locks and visible()
Playwright 1.63.0 (4 Sep 2026) adds named test locks for shared resources, cross-frame frameLocator() without a selector, locator.visible(), richer step metadata, and optional aria/screen snapshots in traces. Experimental CT React/Vue packages freeze; Ubuntu 20.04 dropped. ShopperCove docs checklist only; no affiliate.
4 min read
Summary
Playwright 1.63: test locks, visible locators, richer traces (4 Sep 2026)
Playwright 1.63.0, released on 4 September 2026, adds named test locks so tests that share an external resource never run at the same time, plus frameLocator() without a selector for searching every frame, locator.visible() and optional aria/screen snapshots in traces. It also drops Ubuntu 20.04 and freezes the experimental React and Vue component-testing packages, so retire those CI runners and move CT tests to the stories model before you bump @playwright/test.
Related links
- 01shoppercove.com/blog/vite-plus-1-0-unified-toolchain-october-2026
- 02shoppercove.com/blog/nodejs-26-lts-october-2026-schedule-change
- 03shoppercove.com/blog/nextjs-16-3-8-security-release-2026
Headline features (from the official notes)
Named test locks
Tests that touch a shared resource (external service, global account setting) can declare a named lock. Tests that share a lock name never run concurrently across files, workers, and projects; everything else stays parallel. A test can hold multiple locks; test.describe() can take a lock for a whole group. Details: test locks.
Locate across frames
page.frameLocator() / frame.frameLocator() called without a selector search any frame in the subtree, so you do not have to pin the iframe first. The rest of the locator still resolves inside a single frame; matching elements in several frames throws.
Visible-only locators
locator.visible() returns a locator that matches only visible elements. The release notes recommend it as the replacement for the :visible CSS pseudo-class.
Step params, subtitles, and traces
test.step()acceptssubtitleandparamsfor structured reporter data; API steps also report locator/URL subtitles in the HTML report and trace viewer.- Trace
snapshotscan select{ dom, aria, screen }per action. With aria + screen on, Display Aria in the trace viewer pairs the screenshot with the aria tree.
Other notable APIs / CLI
From the same notes: array-form httpCredentials; opfs in storage state; dialogclosed events; ariaSnapshotJSON(); typed request.get<T>(); standalone reducedMotion / forcedColors / contrast fixture options; --add-reporter; npx playwright install --no-remove; built-in perfetto reporter; HTML report duration waterfall.
Announcements / platform notes
- Experimental
@playwright/experimental-ct-react,@playwright/experimental-ct-react17, and@playwright/experimental-ct-vuewill no longer be updated—migrate to the stories model from 1.62. - Ubuntu 20.04 is not supported anymore.
- On Linux arm64, Playwright now downloads the Chrome for Testing Chromium build (same as other platforms).
Bundled browser versions (1.63)
| Engine | Version |
|---|---|
| Chromium | 153.0.8010.12 |
| Firefox | 155.0 |
| WebKit | 26.6 |
Also tested against Google Chrome 153 and Microsoft Edge 153.
Upgrade checklist
- Inventory: check lockfile /
npm ls @playwright/test(orplaywright). If you are below 1.63.0, schedule the bump in staging. - Install: align
@playwright/test(andplaywrightif used) to 1.63.0+, then runnpx playwright install(use--no-removeif you need to keep other Playwright browser installs). - Adopt carefully: introduce named locks only where tests truly share external state—over-locking serializes the suite.
- CT users: if you still depend on the experimental
*-ct-*packages, follow the stories migration path before they freeze further. - CI OS: retire Ubuntu 20.04 runners for Playwright jobs.
ShopperCove did not change production Playwright versions for this article. Follow the official release notes and your release process.
Bottom line
Playwright 1.63 (4 Sep 2026) is a practical test-runner refresh: test locks, cross-frame frameLocator(), locator.visible(), richer steps/traces, plus CT/Ubuntu announcements. Pin @playwright/test@1.63.0 (or newer) when ready. Read the release notes—prefer them over third-party roundups.
FAQ
What are test locks in Playwright 1.63?
Named locks a test or test.describe() group can declare. Tests sharing a lock name never run concurrently across files, workers or projects. Everything else stays parallel.
What does locator.visible() do?
It returns a locator that matches only visible elements. The release notes recommend it instead of the :visible CSS pseudo-class.
Which browsers ship with Playwright 1.63?
Chromium 153.0.8010.12, Firefox 155.0 and WebKit 26.6. It is also tested against Google Chrome 153 and Microsoft Edge 153.
Sources
Lab evidence
What I found running this
Sources read 5 Oct 2026: playwright.dev release notes; test-parallel#test-locks; GitHub v1.63.0; npm @playwright/test@1.63.0. No suite upgraded on ShopperCove; no benchmarks. Playwright 1.63.0 (4 Sep 2026) adds named test locks for shared resources, cross-frame frameLocator() without a selector, locator.visible(), richer step metadata, and optional aria/screen snapshots in traces. Experimental CT React/Vue packages freeze; Ubuntu 20.04 dropped. ShopperCove docs checklist only.
Explore the product
Untested by us, and no traffic result is guaranteed. Check the live offer and refund terms first.
AI Traffic Secrets for AI-era SEO
See AI Traffic Secrets detailsReady Client Sites for prebuilt websites
See Ready Client Sites detailsKeep reading
Playwright vs Cypress: 1.47s vs 4.24s Smoke
Playwright 1.55.1 Chromium vs Cypress 14.5.4 Electron on one local smoke (visit /, assert h1, click, assert). Warm medians (7 rounds after 1 warm-up): Playwright 1,466 ms vs Cypress 4,243 ms (~2.9x). Disk: PW node_modules ~12 MB + cache ~918 MB; Cypress node_modules ~23 MB + cache ~601 MB. Fixture /workspace/bench-pw-cy/.
Hands-on6 Oct 20264 min read
oxfmt 0.72: native Markdown formatter, Prettier 3.9.9 parity test, sorted imports in code fences (5 Oct 2026)
oxfmt 0.72.0 (5 Oct 2026) swaps its Prettier-backed Markdown path for the native oxc_formatter_markdown (breaking). ShopperCove formatted 221 Markdown drafts with oxfmt 0.71.0, 0.72.0 and Prettier 3.9.9: byte-identical output, ~2 s vs ~16 ms. Plus opt-in import sorting inside code fences, the documented divergences, ignore-file and LSP fixes. No affiliate links.
Summary5 Oct 20265 min read
Biome 2.5.15: type-inference speedups, nursery rules, HTML formatter (30 Sep 2026)
Biome published @biomejs/biome@2.5.15 on 30 September 2026: type-inference and HTML formatter performance, plus nursery rules for React defaults, Svelte runes, logical CSS, and more. ShopperCove upgrade checklist only; no affiliate.
Summary5 Oct 20264 min read
