chore(deps): update dependency @playwright/test to v1.57.0 (!335) · Merge requests · FS Info TU Dortmund / Fachschaftsrat / Finanztools / Finanz-Anordnungsgenerator

This MR contains the following updates:

Package	Change	Age	Confidence
@playwright/test (source)	`1.44.1` -> `1.57.0`

Release Notes

microsoft/playwright (@playwright/test)

`v1.57.0`

Compare Source

Speedboard

In HTML reporter, there's a new tab we call "Speedboard":

It shows you all your executed tests sorted by slowness, and can help you understand where your test suite is taking longer than expected. Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should!

Chrome for Testing

Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.

We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.

If you still see an unexpected behaviour change, please file an issue.

On Arm64 Linux, Playwright continues to use Chromium.

Waiting for webserver output

testConfig.webServer added a wait field. Pass a regular expression, and Playwright will wait until the webserver logs match it.

import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  webServer: {
    command: 'npm run start',
    wait: {
      stdout: '/Listening on port (?<my_server_port>\\d+)/'
    },
  },
});

If you include a named capture group into the expression, then Playwright will provide the capture group contents via environment variables:

import { test, expect } from '@&#8203;playwright/test';

test.use({ baseUrl: `http://localhost:${process.env.MY_SERVER_PORT ?? 3000}` });

test('homepage', async ({ page }) => {
  await page.goto('/');
});

This is not just useful for capturing varying ports of dev servers. You can also use it to wait for readiness of a service that doesn't expose an HTTP readiness check, but instead prints a readiness message to stdout or stderr.

Breaking Change

After 3 years of being deprecated, we removed Page#accessibility from our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.

New APIs

New property testConfig.tag adds a tag to all tests in this run. This is useful when using merge-reports.
worker.on('console') event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. worker.waitForEvent() can be used to wait for it.
locator.description() returns locator description previously set with locator.describe(), and Locator.toString() now uses the description when available.
New option steps in locator.click() and locator.dragTo() that configures the number of mousemove events emitted while moving the mouse pointer to the target element.
Network requests issued by Service Workers are now reported and can be routed through the BrowserContext, only in Chromium. You can opt out using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK environment variable.
Console messages from Service Workers are dispatched through worker.on('console'). You can opt out of this using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE environment variable.

Browser Versions

Chromium 143.0.7499.4
Mozilla Firefox 144.0.2
WebKit 26.0

`v1.56.1`

Compare Source

Highlights

#37871 chore: allow local-network-access permission in chromium #37891 fix(agents): remove workspaceFolder ref from vscode mcp #37759 chore: rename agents to test agents #37757 chore(mcp): fallback to cwd when resolving test config

Browser Versions

Chromium 141.0.7390.37
Mozilla Firefox 142.0.1
WebKit 26.0

`v1.56.0`

Compare Source

Playwright Agents

Introducing Playwright Agents, three custom agent definitions designed to guide LLMs through the core process of building a Playwright test:

🎭 planner explores the app and produces a Markdown test plan
🎭 generator transforms the Markdown plan into the Playwright Test files
🎭 healer executes the test suite and automatically repairs failing tests

Run npx playwright init-agents with your client of choice to generate the latest agent definitions:


# Generate agent files for each agentic loop
# Visual Studio Code
npx playwright init-agents --loop=vscode

# Claude Code
npx playwright init-agents --loop=claude

# opencode
npx playwright init-agents --loop=opencode

[!NOTE] VS Code v1.105 (currently on the VS Code Insiders channel) is needed for the agentic experience in VS Code. It will become stable shortly, we are a bit ahead of times with this functionality!

Learn more about Playwright Agents

New APIs

New methods page.consoleMessages() and page.pageErrors() for retrieving the most recent console messages from the page
New method page.requests() for retrieving the most recent network requests from the page
Added --test-list and --test-list-invert to allow manual specification of specific tests from a file

UI Mode and HTML Reporter

Added option to 'html' reporter to disable the "Copy prompt" button
Added option to 'html' reporter and UI Mode to merge files, collapsing test and describe blocks into a single unified list
Added option to UI Mode mirroring the --update-snapshots options
Added option to UI Mode to run only a single worker at a time

Breaking Changes

Event browserContext.on('backgroundpage') has been deprecated and will not be emitted. Method browserContext.backgroundPages() will return an empty list

Miscellaneous

Aria snapshots render and compare input placeholder
Added environment variable PLAYWRIGHT_TEST to Playwright worker processes to allow discriminating on testing status

Browser Versions

Chromium 141.0.7390.37
Mozilla Firefox 142.0.1
WebKit 26.0

`v1.55.1`

Compare Source

Highlights

#37479 - [Bug]: Upgrade Chromium to 140.0.7339.186. #37147 - [Regression]: Internal error: step id not found. #37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects. #37137 - Revert "fix(a11y): track inert elements as hidden". #37532 - chore: do not use -k option

Browser Versions

Chromium 140.0.7339.186
Mozilla Firefox 141.0
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 139
Microsoft Edge 139

`v1.55.0`

Compare Source

New APIs

New Property testStepInfo.titlePath Returns the full title path starting from the test file, including test and step titles.

Codegen

Automatic toBeVisible() assertions: Codegen can now generate automatic toBeVisible() assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.

Breaking Changes

⚠️ Dropped support for Chromium extension manifest v2.

Miscellaneous

Added support for Debian 13 "Trixie".

Browser Versions

Chromium 140.0.7339.16
Mozilla Firefox 141.0
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 139
Microsoft Edge 139

`v1.54.2`

Compare Source

Highlights

#36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error) #36828 - [Regression]: Playwright Codegen keeps spamming with selected option #36810 - [Regression]: Starting Codegen with target language doesn't work anymore

Browser Versions

Chromium 139.0.7258.5
Mozilla Firefox 140.0.2
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 140
Microsoft Edge 140

`v1.54.1`

Compare Source

Highlights

#36650 - [Regression]: 1.54.0 breaks downloading browsers when an HTTP(S) proxy is used

Browser Versions

Chromium 139.0.7258.5
Mozilla Firefox 140.0.2
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 140
Microsoft Edge 140

`v1.54.0`

Compare Source

Highlights

New cookie property partitionKey in browserContext.cookies() and browserContext.addCookies(). This property allows to save and restore partitioned cookies. See CHIPS MDN article for more information. Note that browsers have different support and defaults for cookie partitioning.

New option noSnippets to disable code snippets in the html report.

import { defineConfig } from '@&#8203;playwright/test';

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

New property location in test annotations, for example in testResult.annotations and testInfo.annotations. It shows where the annotation like test.skip or test.fixme was added.

Command Line

New option --user-data-dir in multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.
```
npx playwright codegen --user-data-dir=./user-data
```
Option -gv has been removed from the npx playwright test command. Use --grep-invert instead.
npx playwright open does not open the test recorder anymore. Use npx playwright codegen instead.

Miscellaneous

Support for Node.js 16 has been removed.
Support for Node.js 18 has been deprecated, and will be removed in the future.

Browser Versions

Chromium 139.0.7258.5
Mozilla Firefox 140.0.2
WebKit 26.0

This version was also tested against the following stable channels:

Google Chrome 140
Microsoft Edge 140

`v1.53.2`

Compare Source

Highlights

#36317 - [Regression]: Merging pre-1.53 blob reports loses attachments #36357 - [Regression (Chromium)]: CDP missing trailing slash #36292 - [Bug (MSEdge)]: Edge fails to launch when using msRelaunchNoCompatLayer

Browser Versions

Chromium 138.0.7204.23
Mozilla Firefox 139.0
WebKit 18.5

This version was also tested against the following stable channels:

Google Chrome 137
Microsoft Edge 137

`v1.53.1`

Compare Source

Highlights

#36339 - [Regression]: Click can fail when scrolling required #36307 - [Regression (Chromium)]: Under some scenarios filling a textarea doesn't fill #36294 - [Regression (Firefox)]: setViewportSize times out #36350 - [Fix]: Display HTTP method for fetch trace entries

Browser Versions

Chromium 138.0.7204.23
Mozilla Firefox 139.0
WebKit 18.5

This version was also tested against the following stable channels:

Google Chrome 137
Microsoft Edge 137

`v1.53.0`

Compare Source

Trace Viewer and HTML Reporter Updates

New Steps in Trace Viewer and HTML reporter:

New option in 'html' reporter to set the title of a specific test run:

import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  reporter: [['html', { title: 'Custom test run #&#8203;1028' }]]
});

Miscellaneous

New option kind in testInfo.snapshotPath() controls which snapshot path template is used.

New method locator.describe() to describe a locator. Used for trace viewer and reports.

const button = page.getByTestId('btn-sub').describe('Subscribe button');
await button.click();

npx playwright install --list will now list all installed browsers, versions and locations.

Browser Versions

Chromium 138.0.7204.4
Mozilla Firefox 139.0
WebKit 18.5

This version was also tested against the following stable channels:

Google Chrome 137
Microsoft Edge 137

`v1.52.0`

Compare Source

Highlights

New method expect(locator).toContainClass() to ergonomically assert individual class names on the element.
```
await expect(page.getByRole('listitem', { name: 'Ship v1.52' })).toContainClass('done');
```

Aria Snapshots got two new properties: /children for strict matching and /url for links.

await expect(locator).toMatchAriaSnapshot(`
  - list
    - /children: equal
    - listitem: Feature A
    - listitem:
      - link "Feature B":
        - /url: "https://playwright.dev"
`);

Test Runner

New property testProject.workers allows to specify the number of concurrent worker processes to use for a test project. The global limit of property testConfig.workers still applies.
New testConfig.failOnFlakyTests option to fail the test run if any flaky tests are detected, similarly to --fail-on-flaky-tests. This is useful for CI/CD environments where you want to ensure that all tests are stable before deploying.
New property testResult.annotations contains annotations for each test retry.

Miscellaneous

New option maxRedirects in apiRequest.newContext() to control the maximum number of redirects.
HTML reporter now supports NOT filtering via !@my-tag or !my-file.spec.ts or !p:my-project.

Breaking Changes

Changes to glob URL patterns in methods like page.route():
- ? wildcard is not supported any more, it will always match question mark ? character.
- Ranges/sets [] are not supported anymore. We recommend using regular expressions instead.
Method route.continue() does not allow to override the Cookie header anymore. If a Cookie header is provided, it will be ignored, and the cookie will be loaded from the browser's cookie store. To set custom cookies, use browserContext.addCookies().
macOS 13 is now deprecated and will no longer receive WebKit updates. Please upgrade to a more recent macOS version to continue benefiting from the latest WebKit improvements.

Browser Versions

Chromium 136.0.7103.25
Mozilla Firefox 137.0
WebKit 18.4

This version was also tested against the following stable channels:

Google Chrome 135
Microsoft Edge 135

`v1.51.1`

Compare Source

Highlights

#35093 - [Regression]: TimeoutOverflowWarning: 2149630.634 does not fit into a 32-bit signed integer #35138 - [Regression]: TypeError: Cannot read properties of undefined (reading 'expectInfo')

Browser Versions

Chromium 134.0.6998.35
Mozilla Firefox 135.0
WebKit 18.4

This version was also tested against the following stable channels:

Google Chrome 133
Microsoft Edge 133

`v1.51.0`

Compare Source

StorageState for indexedDB

New option indexedDB for browserContext.storageState() allows to save and restore IndexedDB contents. Useful when your application uses IndexedDB API to store authentication tokens, like Firebase Authentication.

Here is an example following the authentication guide:

// tests/auth.setup.ts
import { test as setup, expect } from '@&#8203;playwright/test';
import path from 'path';

const authFile = path.join(__dirname, '../playwright/.auth/user.json');

setup('authenticate', async ({ page }) => {
  await page.goto('/');
  // ... perform authentication steps ...

  // make sure to save indexedDB
  await page.context().storageState({ path: authFile, indexedDB: true });
});

Copy prompt

New "Copy prompt" button on errors in the HTML report, trace viewer and UI mode. Click to copy a pre-filled LLM prompt that contains the error message and useful context for fixing the error.

Filter visible elements

New option visible for locator.filter() allows matching only visible elements.

// example.spec.ts
test('some test', async ({ page }) => {
  // Ignore invisible todo items.
  const todoItems = page.getByTestId('todo-item').filter({ visible: true });
  // Check there are exactly 3 visible ones.
  await expect(todoItems).toHaveCount(3);
});

Git information in HTML report

Set option testConfig.captureGitInfo to capture git information into testConfig.metadata.

// playwright.config.ts
import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  captureGitInfo: { commit: true, diff: true }
});

HTML report will show this information when available:

Test Step improvements

A new TestStepInfo object is now available in test steps. You can add step attachments or skip the step under some conditions.

test('some test', async ({ page, isMobile }) => {
  // Note the new "step" argument:
  await test.step('here is my step', async step => {
    step.skip(isMobile, 'not relevant on mobile layouts');

    // ...
    await step.attach('my attachment', { body: 'some text' });
    // ...
  });
});

Miscellaneous

New option contrast for methods page.emulateMedia() and browser.newContext() allows to emulate the prefers-contrast media feature.
New option failOnStatusCode makes all fetch requests made through the APIRequestContext throw on response codes other than 2xx and 3xx.
Assertion expect(page).toHaveURL() now supports a predicate.

Browser Versions

Chromium 134.0.6998.35
Mozilla Firefox 135.0
WebKit 18.4

This version was also tested against the following stable channels:

Google Chrome 133
Microsoft Edge 133

`v1.50.1`

Compare Source

Highlights

#34483 - [Feature]: single aria snapshot for different engines/browsers #34497 - [Bug]: Firefox not handling keepalive: true fetch requests #34504 - [Bug]: update snapshots not creating good diffs #34507 - [Bug]: snapshotPathTemplate doesnt work when multiple projects #34462 - [Bug]: updateSnapshots "changed" throws an error

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

`v1.50.0`

Compare Source

Test runner

New option timeout allows specifying a maximum run time for an individual test step. A timed-out step will fail the execution of the test.

test('some test', async ({ page }) => {
  await test.step('a step', async () => {
    // This step can time out separately from the test
  }, { timeout: 1000 });
});

New method test.step.skip() to disable execution of a test step.

test('some test', async ({ page }) => {
  await test.step('before running step', async () => {
    // Normal step
  });

  await test.step.skip('not yet ready', async () => {
    // This step is skipped
  });

  await test.step('after running step', async () => {
    // This step still runs even though the previous one was skipped
  });
});

Expanded expect(locator).toMatchAriaSnapshot() to allow storing of aria snapshots in separate YAML files.
Added method expect(locator).toHaveAccessibleErrorMessage() to assert the Locator points to an element with a given aria errormessage.
Option testConfig.updateSnapshots added the configuration enum changed. changed updates only the snapshots that have changed, whereas all now updates all snapshots, regardless of whether there are any differences.
New option testConfig.updateSourceMethod defines the way source code is updated when testConfig.updateSnapshots is configured. Added overwrite and 3-way modes that write the changes into source code, on top of existing patch mode that creates a patch file.
```
npx playwright test --update-snapshots=changed --update-source-method=3way
```
Option testConfig.webServer added a gracefulShutdown field for specifying a process kill signal other than the default SIGKILL.
Exposed testStep.attachments from the reporter API to allow retrieval of all attachments created by that step.
New option pathTemplate for toHaveScreenshot and toMatchAriaSnapshot assertions in the testConfig.expect configuration.

UI updates

Updated default HTML reporter to improve display of attachments.
New button for picking elements to produce aria snapshots.
Additional details (such as keys pressed) are now displayed alongside action API calls in traces.
Display of canvas content in traces is error-prone. Display is now disabled by default, and can be enabled via the Display canvas content UI setting.
Call and Network panels now display additional time information.

Breaking

expect(locator).toBeEditable() and locator.isEditable() now throw if the target element is not <input>, <select>, or a number of other editable elements.
Option testConfig.updateSnapshots now updates all snapshots when set to all, rather than only the failed/changed snapshots. Use the new enum changed to keep the old functionality of only updating the changed snapshots.

Browser Versions

Chromium 133.0.6943.16
Mozilla Firefox 134.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 132
Microsoft Edge 132

`v1.49.1`

Compare Source

Highlights

#33802 - [Bug]: Codegen's Clear button doesn't work if not recording #33806 - [Bug]: playwright hangs while waiting for pending navigations #33787 - [Bug]: VSC extension isn't capturing all entered text #33788 - [Regression]: Double clicking the steps in trace viewer doesn't filter actions #33772 - [Bug]: aria_snapshot generates invalid yaml when combined with an aria-label attribut #33791 - [Bug]: text input with number value raises "container is not iterable" with to_match_aria_snapshot #33644 - [Bug]: getByRole can't find element with the accessible name from label element when aria-labelledby is not valid #33660 - [Regression]: Unable to open Playwright UI in Dark Mode

Browser Versions

Chromium 131.0.6778.33
Mozilla Firefox 132.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 130
Microsoft Edge 130

`v1.49.0`

Compare Source

Aria snapshots

New assertion expect(locator).toMatchAriaSnapshot() verifies page structure by comparing to an expected accessibility tree, represented as YAML.

await page.goto('https://playwright.dev');
await expect(page.locator('body')).toMatchAriaSnapshot(`
  - banner:
    - heading /Playwright enables reliable/ [level=1]
    - link "Get started"
    - link "Star microsoft/playwright on GitHub"
  - main:
    - img "Browsers (Chromium, Firefox, WebKit)"
    - heading "Any browser • Any platform • One API"
`);

You can generate this assertion with Test Generator and update the expected snapshot with --update-snapshots command line flag.

Learn more in the aria snapshots guide.

Test runner

New option testConfig.tsconfig allows to specify a single tsconfig to be used for all tests.
New method test.fail.only() to focus on a failing test.
Options testConfig.globalSetup and testConfig.globalTeardown now support multiple setups/teardowns.
New value 'on-first-failure' for testOptions.screenshot.
Added "previous" and "next" buttons to the HTML report to quickly switch between test cases.
New properties testInfoError.cause and testError.cause mirroring Error.cause.

Breaking: channels `chrome`, `msedge` and similar switch to new headless

This change affects you if you're using one of the following channels in your playwright.config.ts:

chrome, chrome-dev, chrome-beta, or chrome-canary
msedge, msedge-dev, msedge-beta, or msedge-canary

What do I need to do?

After updating to Playwright v1.49, run your test suite. If it still passes, you're good to go. If not, you will probably need to update your snapshots, and adapt some of your test code around PDF viewers and extensions. See issue #33566 for more details.

Other breaking changes

There will be no more updates for WebKit on Ubuntu 20.04 and Debian 11. We recommend updating your OS to a later version.
Package @playwright/experimental-ct-vue2 will no longer be updated.
Package @playwright/experimental-ct-solid will no longer be updated.

Try new Chromium headless

You can opt into the new headless mode by using 'chromium' channel. As official Chrome documentation puts it:

New Headless on the other hand is the real Chrome browser, and is thus more authentic, reliable, and offers more features. This makes it more suitable for high-accuracy end-to-end web app testing or browser extension testing.

See issue #33566 for the list of possible breakages you could encounter and more details on Chromium headless. Please file an issue if you see any problems after opting in.

import { defineConfig, devices } from '@&#8203;playwright/test';

export default defineConfig({
  projects: [
    {
      name: 'chromium',
      use: { ...devices['Desktop Chrome'], channel: 'chromium' },
    },
  ],
});

Miscellaneous

<canvas> elements inside a snapshot now draw a preview.
New method tracing.group() to visually group actions in the trace.
Playwright docker images switched from Node.js v20 to Node.js v22 LTS.

Browser Versions

Chromium 131.0.6778.33
Mozilla Firefox 132.0
WebKit 18.2

This version was also tested against the following stable channels:

Google Chrome 130
Microsoft Edge 130

`v1.48.2`

Compare Source

Highlights

#33141 - [Bug]: UI Mode crashed #33219 - [BUG] Trace Viewer PWA crashes with "Aw, Snap!" #33086 - [Bug]: UI Mode Memory problem #33000 - [Regression]: Inspector and Browser doesn't close on CTRL+C #33204 - [Bug]: Chrome tab and inspector not closing after terminating session in terminal

Browser Versions

Chromium 130.0.6723.19
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 129
Microsoft Edge 129

`v1.48.1`

Compare Source

Highlights

#33023 - [Bug]: command line flag --headed has no effect in ui mode #33107 - [REGRESSION]: page.waitForRequest does not get resolved since 1.48.0 #33085 - [Bug]: WebSocket route does not handle full URLs in Playwright #33052 - [Regression]: Inspector not showing recorded steps #33132 - [Bug]: Wrong Ubuntu release name in Dockerfile.noble #32996 - [BUG] Trace attachments have small unusable height

Browser Versions

Chromium 130.0.6723.19
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 129
Microsoft Edge 129

`v1.48.0`

Compare Source

WebSocket routing

New methods page.routeWebSocket() and browserContext.routeWebSocket() allow to intercept, modify and mock WebSocket connections initiated in the page. Below is a simple example that mocks WebSocket communication by responding to a "request" with a "response".

await page.routeWebSocket('/ws', ws => {
  ws.onMessage(message => {
    if (message === 'request')
      ws.send('response');
  });
});

See WebSocketRoute for more details.

UI updates

New "copy" buttons for annotations and test location in the HTML report.
Route method calls like route.fulfill() are not shown in the report and trace viewer anymore. You can see which network requests were routed in the network tab instead.
New "Copy as cURL" and "Copy as fetch" buttons for requests in the network tab.

Miscellaneous

Option form and similar ones now accept FormData.
New method page.requestGC() may help detect memory leaks.
New option location to pass custom step location.
Requests made by APIRequestContext now record detailed timing and security information in the HAR.

Browser Versions

Chromium 130.0.6723.19
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 129
Microsoft Edge 129

`v1.47.2`

Compare Source

Highlights

https://github.com/microsoft/playwright/pull/32699- [REGRESSION]: fix(codegen): use content_frame property in python/.NET https://github.com/microsoft/playwright/issues/32706- [REGRESSION]: page.pause() does not pause test timeout after 1.47 #32661 - fix(trace-viewer): time delta between local and remote actions

Browser Versions

Chromium 129.0.6668.29
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 128
Microsoft Edge 128

`v1.47.1`

Compare Source

Highlights

#32480 - [REGRESSION]: tsconfig.json's compilerOptions.paths no longer working in 1.47 #32552 - [REGRESSION]: broken UI in Trace Viewer while showing network response body

Browser Versions

Chromium 129.0.6668.29
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 128
Microsoft Edge 128

`v1.47.0`

Compare Source

Network Tab improvements

The Network tab in the UI mode and trace viewer has several nice improvements:

filtering by asset type and URL
better display of query string parameters
preview of font assets

Credit to @kubajanik for these wonderful improvements!

`--tsconfig` CLI option

By default, Playwright will look up the closest tsconfig for each imported file using a heuristic. You can now specify a single tsconfig file in the command line, and Playwright will use it for all imported files, not only test files:


# Pass a specific tsconfig
npx playwright test --tsconfig tsconfig.test.json

APIRequestContext now accepts `URLSearchParams` and `string` as query parameters

You can now pass URLSearchParams and string as query parameters to APIRequestContext:

test('query params', async ({ request }) => {
  const searchParams = new URLSearchParams();
  searchParams.set('userId', 1);
  const response = await request.get(
      'https://jsonplaceholder.typicode.com/posts',
      {
        params: searchParams // or as a string: 'userId=1'
      }
  );
  // ...
});

Miscellaneous

The mcr.microsoft.com/playwright:v1.47.0 now serves a Playwright image based on Ubuntu 24.04 Noble. To use the 22.04 jammy-based image, please use mcr.microsoft.com/playwright:v1.47.0-jammy instead.
The :latest/:focal/:jammy tag for Playwright Docker images is no longer being published. Pin to a specific version for better stability and reproducibility.
New option behavior in page.removeAllListeners(), browser.removeAllListeners() and browserContext.removeAllListeners() to wait for ongoing listeners to complete.
TLS client certificates can now be passed from memory by passing cert and key as buffers instead of file paths.
Attachments with a text/html content type can now be opened in a new tab in the HTML report. This is useful for including third-party reports or other HTML content in the Playwright test report and distributing it to your team.
noWaitAfter in locator.selectOption() was deprecated.
We've seen reports of WebGL in Webkit misbehaving on GitHub Actions macos-13. We recommend upgrading GitHub Actions to macos-14.

Browser Versions

Chromium 129.0.6668.29
Mozilla Firefox 130.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 128
Microsoft Edge 128

`v1.46.1`

Compare Source

Highlights

#32004 - [REGRESSION]: Client Certificates don't work with Microsoft IIS #32004 - [REGRESSION]: Websites stall on TLS handshake errors when using Client Certificates #32146 - [BUG]: Credential scanners warn about internal socks-proxy TLS certificates #32056 - [REGRESSION]: 1.46.0 (TypeScript) - custom fixtures extend no longer chainable #32070 - [Bug]: --only-changed flag and project dependencies #32188 - [Bug]: --only-changed with shallow clone throws "unknown revision" error

Browser Versions

Chromium 128.0.6613.18
Mozilla Firefox 128.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 127
Microsoft Edge 127

`v1.46.0`

Compare Source

TLS Client Certificates

Playwright now allows to supply client-side certificates, so that server can verify them, as specified by TLS Client Authentication.

When client certificates are specified, all browser traffic is routed through a proxy that establishes the secure TLS connection, provides client certificates to the server and validates server certificates.

The following snippet sets up a client certificate for https://example.com:

import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  // ...
  use: {
    clientCertificates: [{
      origin: 'https://example.com',
      certPath: './cert.pem',
      keyPath: './key.pem',
      passphrase: 'mysecretpassword',
    }],
  },
  // ...
});

You can also provide client certificates to a particular test project or as a parameter of browser.newContext() and apiRequest.newContext().

`--only-changed` cli option

New CLI option --only-changed allows to only run test files that have been changed since the last git commit or from a specific git "ref".


# Only run test files with uncommitted changes
npx playwright test --only-changed

# Only run test files changed relative to the "main" branch
npx playwright test --only-changed=main

Component Testing: New `router` fixture

This release introduces an experimental router fixture to intercept and handle network requests in component testing. There are two ways to use the router fixture:

Call router.route(url, handler) that behaves similarly to page.route().
Call router.use(handlers) and pass MSW library request handlers to it.

Here is an example of reusing your existing MSW handlers in the test.

import { handlers } from '@&#8203;src/mocks/handlers';

test.beforeEach(async ({ router }) => {
  // install common handlers before each test
  await router.use(...handlers);
});

test('example test', async ({ mount }) => {
  // test as usual, your handlers are active
  // ...
});

This fixture is only available in component tests.

UI Mode / Trace Viewer Updates

Test annotations are now shown in UI mode.
Content of text attachments is now rendered inline in the attachments pane.
New setting to show/hide routing actions like route.continue().
Request method and status are shown in the network details tab.
New button to copy source file location to clipboard.
Metadata pane now displays the baseURL.

Miscellaneous

New maxRetries option in apiRequestContext.fetch() which retries on the ECONNRESET network error.
New option to box a fixture to minimize the fixture exposure in test reports and error messages.
New option to provide a custom fixture title to be used in test reports and error messages.

Possibly breaking change

Fixture values that are array of objects, when specified in the test.use() block, may require being wrapped into a fixture tuple. This is best seen on the example:

import { test as base } from '@&#8203;playwright/test';

// Define an option fixture that has an "array of objects" value
type User = { name: string, password: string };
const test = base.extend<{ users: User[] }>({
  users: [ [], { option: true } ],
}); 

// Specify option value in the test.use block.
test.use({
  // WRONG: this syntax may not work for you
  users: [
    { name: 'John Doe', password: 'secret' },
    { name: 'John Smith', password: 's3cr3t' },
  ],
  // CORRECT: this syntax will work. Note extra [] around the value, and the "scope" property.
  users: [[
    { name: 'John Doe', password: 'secret' },
    { name: 'John Smith', password: 's3cr3t' },
  ], { scope: 'test' }],
});

test('example test', async () => {
  // ...
});

Browser Versions

Chromium 128.0.6613.18
Mozilla Firefox 128.0
WebKit 18.0

This version was also tested against the following stable channels:

Google Chrome 127
Microsoft Edge 127

`v1.45.3`

Compare Source

Highlights

#31764 - [Bug]: some actions do not appear in the trace file microsoft/playwright-java#1617 - [Bug]: Traceviewer not reporting all actions

Browser Versions

Chromium 127.0.6533.5
Mozilla Firefox 127.0
WebKit 17.4

This version was also tested against the following stable channels:

Google Chrome 126
Microsoft Edge 126

`v1.45.2`

Compare Source

Highlights

#31613 - [REGRESSION]: Trace is not showing any screenshots nor test name #31601 - [REGRESSION]: missing trace for 2nd browser #31541 - [REGRESSION]: Failing tests have a trace with no images and with steps missing

Browser Versions

Chromium 127.0.6533.5
Mozilla Firefox 127.0
WebKit 17.4

This version was also tested against the following stable channels:

Google Chrome 126
Microsoft Edge 126

`v1.45.1`

Compare Source

Highlights

#31473 - [REGRESSION]: Playwright raises an error ENOENT: no such file or directory, open 'test-results/.playwright-artifacts-0/hash.zip' with Electron #31442 - [REGRESSION]: Locators of elements changing from/to hidden have operations hanging when using --disable-web-security #31431 - [REGRESSION]: NewTab doesn't work properly with Chrome with --disable-web-security #31425 - [REGRESSION]: beforeEach hooks are not skipped when describe condition depends on fixtures #31491 - [REGRESSION]: @playwright/experimental-ct-react doesn't work with VSCode extension and PNPM

Browser Versions

Chromium 127.0.6533.5
Mozilla Firefox 127.0
WebKit 17.4

This version was also tested against the following stable channels:

Google Chrome 126
Microsoft Edge 126

`v1.45.0`

Compare Source

Clock

Utilizing the new Clock API allows to manipulate and control time within tests to verify time-related behavior. This API covers many common scenarios, including:

testing with predefined time;
keeping consistent time and timers;
monitoring inactivity;
ticking through time manually.

// Initialize clock and let the page load naturally.
await page.clock.install({ time: new Date('2024-02-02T08:00:00') });
await page.goto('http://localhost:3333');

// Pretend that the user closed the laptop lid and opened it again at 10am,
// Pause the time once reached that point.
await page.clock.pauseAt(new Date('2024-02-02T10:00:00'));

// Assert the page state.
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:00:00 AM');

// Close the laptop lid again and open it at 10:30am.
await page.clock.fastForward('30:00');
await expect(page.getByTestId('current-time')).toHaveText('2/2/2024, 10:30:00 AM');

See the clock guide for more details.

Test runner

New CLI option --fail-on-flaky-tests that sets exit code to 1 upon any flaky tests. Note that by default, the test runner exits with code 0 when all failed tests recovered upon a retry. With this option, the test run will fail in such case.
New enviroment variable PLAYWRIGHT_FORCE_TTY controls whether built-in list, line and dot reporters assume a live terminal. For example, this could be useful to disable tty behavior when your CI environment does not handle ANSI control sequences well. Alternatively, you can enable tty behavior even when to live terminal is present, if you plan to post-process the output and handle control sequences.
```
# Avoid TTY features that output ANSI control sequences
PLAYWRIGHT_FORCE_TTY=0 npx playwright test

# Enable TTY features, assuming a terminal width 80
PLAYWRIGHT_FORCE_TTY=80 npx playwright test
```
New options testConfig.respectGitIgnore and testProject.respectGitIgnore control whether files matching .gitignore patterns are excluded when searching for tests.

New property timeout is now available for custom expect matchers. This property takes into account playwright.config.ts and expect.configure().

import { expect as baseExpect } from '@&#8203;playwright/test';

export const expect = baseExpect.extend({
  async toHaveAmount(locator: Locator, expected: number, options?: { timeout?: number }) {
    // When no timeout option is specified, use the config timeout.
    const timeout = options?.timeout ?? this.timeout;
    // ... implement the assertion ...
  },
});

Miscellaneous

Method locator.setInputFiles() now supports uploading a directory for <input type=file webkitdirectory> elements.
```
await page.getByLabel('Upload directory').setInputFiles(path.join(__dirname, 'mydir'));
```
Multiple methods like locator.click() or locator.press() now support a ControlOrMeta modifier key. This key maps to Meta on macOS and maps to Control on Windows and Linux.
```
// Press the common keyboard shortcut Control+S or Meta+S to trigger a "Save" operation.
await page.keyboard.press('ControlOrMeta+S');
```
New property httpCredentials.send in apiRequest.newContext() that allows to either always send the Authorization header or only send it in response to 401 Unauthorized.
New option reason in apiRequestContext.dispose() that will be included in the error message of ongoing operations interrupted by the context disposal.
New option host in browserType.launchServer() allows to accept websocket connections on a specific address instead of unspecified 0.0.0.0.
Playwright now supports Chromium, Firefox and WebKit on Ubuntu 24.04.
v1.45 is the last release to receive WebKit update for macOS 12 Monterey. Please update macOS to keep using the latest WebKit.

Browser Versions

Chromium 127.0.6533.5
Mozilla Firefox 127.0
WebKit 17.4

This version was also tested against the following stable channels:

Google Chrome 126
Microsoft Edge 126

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

Edited Nov 28, 2025 by Renovate Bot

chore(deps): update dependency @playwright/test to v1.57.0

Release Notes

Speedboard

Chrome for Testing

Waiting for webserver output

Breaking Change

New APIs

Browser Versions

Highlights

Browser Versions

Playwright Agents

New APIs

UI Mode and HTML Reporter

Breaking Changes

Miscellaneous

Browser Versions

Highlights

Browser Versions

New APIs

Codegen

Breaking Changes

Miscellaneous

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Highlights

Command Line

Miscellaneous

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Trace Viewer and HTML Reporter Updates

Miscellaneous

Browser Versions

Highlights

Test Runner

Miscellaneous

Breaking Changes

Browser Versions

Highlights

Browser Versions

StorageState for indexedDB

Copy prompt

Filter visible elements

Git information in HTML report

Test Step improvements

Miscellaneous

Browser Versions

Highlights

Browser Versions

Test runner

UI updates

Breaking

Browser Versions

Highlights

Browser Versions

Aria snapshots

Test runner

Breaking: channels chrome, msedge and similar switch to new headless

What do I need to do?

Other breaking changes

Try new Chromium headless

Miscellaneous

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

WebSocket routing

UI updates

Miscellaneous

Browser Versions

Highlights

Browser Versions

Highlights

Browser Versions

Breaking: channels `chrome`, `msedge` and similar switch to new headless

`--tsconfig` CLI option

APIRequestContext now accepts `URLSearchParams` and `string` as query parameters

`--only-changed` cli option

Component Testing: New `router` fixture