kjuulh/lebusiness-client
1
0
Fork 0
Code Issues 1 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

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

Open
kjuulh wants to merge 1 commits from renovate/playwright-monorepo into main
pull from: renovate/playwright-monorepo
merge into: kjuulh:main
Conversation 0 Commits 1 Files Changed 1 +22 -22
kjuulh commented 2025-03-26 00:04:01 +01:00
Owner
Copy Link

This PR contains the following updates:

Package Type Update Change
@playwright/test (source) devDependencies minor 1.50.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":

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.

new and old logo

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 '@​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

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

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

https://github.com/microsoft/playwright/issues/37479 - [Bug]: Upgrade Chromium to 140.0.7339.186.
https://github.com/microsoft/playwright/issues/37147 - [Regression]: Internal error: step id not found.
https://github.com/microsoft/playwright/issues/37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects.
https://github.com/microsoft/playwright/pull/37137 - Revert "fix(a11y): track inert elements as hidden".
https://github.com/microsoft/playwright/pull/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

https://github.com/microsoft/playwright/issues/36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)
https://github.com/microsoft/playwright/issues/36828 - [Regression]: Playwright Codegen keeps spamming with selected option
https://github.com/microsoft/playwright/issues/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

https://github.com/microsoft/playwright/issues/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

https://github.com/microsoft/playwright/issues/36317 - [Regression]: Merging pre-1.53 blob reports loses attachments
https://github.com/microsoft/playwright/pull/36357 - [Regression (Chromium)]: CDP missing trailing slash
https://github.com/microsoft/playwright/issues/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

https://github.com/microsoft/playwright/issues/36339 - [Regression]: Click can fail when scrolling required
https://github.com/microsoft/playwright/issues/36307 - [Regression (Chromium)]: Under some scenarios filling a textarea doesn't fill
https://github.com/microsoft/playwright/issues/36294 - [Regression (Firefox)]: setViewportSize times out
https://github.com/microsoft/playwright/pull/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 Trace Viewer Steps

  • 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 !@&#8203;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

https://github.com/microsoft/playwright/issues/35093 - [Regression]: TimeoutOverflowWarning: 2149630.634 does not fit into a 32-bit signed integer
https://github.com/microsoft/playwright/issues/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.

Copy prompt

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:

Git information in the report

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

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

Configuration

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

🚦 Automerge: Enabled.

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

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

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@playwright/test](https://playwright.dev) ([source](https://github.com/microsoft/playwright)) | devDependencies | minor | [`1.50.1` -> `1.57.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.50.1/1.57.0) | --- ### Release Notes <details> <summary>microsoft/playwright (@&#8203;playwright/test)</summary> ### [`v1.57.0`](https://github.com/microsoft/playwright/releases/tag/v1.57.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.56.1...v1.57.0) #### Speedboard In HTML reporter, there's a new tab we call "Speedboard": <img width="600" alt="speedboard" src="https://github.com/user-attachments/assets/4ba117ea-ea94-4b6a-82b2-8bbd00dfe81c" /> 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](https://developer.chrome.com/blog/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. <img width="500" alt="new and old logo" src="https://github.com/user-attachments/assets/e9a5c4f2-9f35-4c27-9382-0f5eda377097" /> If you still see an unexpected behaviour change, please [file an issue](https://github.com/microsoft/playwright/issues/new). On Arm64 Linux, Playwright continues to use Chromium. #### Waiting for webserver output [testConfig.webServer](https://playwright.dev/docs/api/class-testconfig#test-config-web-server) added a `wait` field. Pass a regular expression, and Playwright will wait until the webserver logs match it. ```js 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: ```js 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](https://www.deque.com/axe/) if you need to test page accessibility. See our Node.js [guide](https://playwright.dev/docs/accessibility-testing) for integration with Axe. #### New APIs - New property [testConfig.tag](https://playwright.dev/docs/api/class-testconfig#test-config-tag) adds a tag to all tests in this run. This is useful when using [merge-reports](https://playwright.dev/docs/test-sharding#merging-reports-from-multiple-shards). - [worker.on('console')](https://playwright.dev/docs/api/class-worker#worker-event-console) event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. [worker.waitForEvent()](https://playwright.dev/docs/api/class-worker#worker-wait-for-event) can be used to wait for it. - [locator.description()](https://playwright.dev/docs/api/class-locator#locator-description) returns locator description previously set with [locator.describe()](https://playwright.dev/docs/api/class-locator#locator-describe), and `Locator.toString()` now uses the description when available. - New option [`steps`](https://playwright.dev/docs/api/class-locator#locator-click-option-steps) in [locator.click()](https://playwright.dev/docs/api/class-locator#locator-click) and [locator.dragTo()](https://playwright.dev/docs/api/class-locator#locator-drag-to) that configures the number of `mousemove` events emitted while moving the mouse pointer to the target element. - Network requests issued by [Service Workers](https://playwright.dev/docs/service-workers#network-events-and-routing) are now reported and can be routed through the [BrowserContext](https://playwright.dev/docs/api/class-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')](https://playwright.dev/docs/api/class-worker#worker-event-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`](https://github.com/microsoft/playwright/releases/tag/v1.56.1) [Compare Source](https://github.com/microsoft/playwright/compare/v1.56.0...v1.56.1) #### Highlights [#&#8203;37871](https://github.com/microsoft/playwright/issues/37871) chore: allow local-network-access permission in chromium [#&#8203;37891](https://github.com/microsoft/playwright/issues/37891) fix(agents): remove workspaceFolder ref from vscode mcp [#&#8203;37759](https://github.com/microsoft/playwright/issues/37759) chore: rename agents to test agents [#&#8203;37757](https://github.com/microsoft/playwright/issues/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`](https://github.com/microsoft/playwright/releases/tag/v1.56.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.55.1...v1.56.0) #### 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: ```bash ### 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](https://playwright.dev/docs/test-agents) #### New APIs - New methods [page.consoleMessages()](https://playwright.dev/docs/api/class-page#page-console-messages) and [page.pageErrors()](https://playwright.dev/docs/api/class-page#page-page-errors) for retrieving the most recent console messages from the page - New method [page.requests()](https://playwright.dev/docs/api/class-page#page-requests) for retrieving the most recent network requests from the page - Added [`--test-list` and `--test-list-invert`](https://playwright.dev/docs/test-cli#test-list) 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')](https://playwright.dev/docs/api/class-browsercontext#browser-context-event-background-page) has been deprecated and will not be emitted. Method [browserContext.backgroundPages()](https://playwright.dev/docs/api/class-browsercontext#browser-context-background-pages) 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`](https://github.com/microsoft/playwright/releases/tag/v1.55.1) [Compare Source](https://github.com/microsoft/playwright/compare/v1.55.0...v1.55.1) ##### Highlights https://github.com/microsoft/playwright/issues/37479 - \[Bug]: Upgrade Chromium to 140.0.7339.186. https://github.com/microsoft/playwright/issues/37147 - \[Regression]: Internal error: step id not found. https://github.com/microsoft/playwright/issues/37146 - \[Regression]: HTML reporter displays a broken chip link when there are no projects. https://github.com/microsoft/playwright/pull/37137 - Revert "fix(a11y): track inert elements as hidden". https://github.com/microsoft/playwright/pull/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`](https://github.com/microsoft/playwright/releases/tag/v1.55.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.54.2...v1.55.0) #### New APIs - New Property [testStepInfo.titlePath](https://playwright.dev/docs/api/class-teststepinfo#test-step-info-title-path) 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`](https://github.com/microsoft/playwright/releases/tag/v1.54.2) [Compare Source](https://github.com/microsoft/playwright/compare/v1.54.1...v1.54.2) ##### Highlights https://github.com/microsoft/playwright/issues/36714 - \[Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error) https://github.com/microsoft/playwright/issues/36828 - \[Regression]: Playwright Codegen keeps spamming with selected option https://github.com/microsoft/playwright/issues/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`](https://github.com/microsoft/playwright/releases/tag/v1.54.1) [Compare Source](https://github.com/microsoft/playwright/compare/v1.54.0...v1.54.1) ##### Highlights https://github.com/microsoft/playwright/issues/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`](https://github.com/microsoft/playwright/releases/tag/v1.54.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.53.2...v1.54.0) #### Highlights - New cookie property `partitionKey` in [browserContext.cookies()](https://playwright.dev/docs/api/class-browsercontext#browser-context-cookies) and [browserContext.addCookies()](https://playwright.dev/docs/api/class-browsercontext#browser-context-add-cookies). This property allows to save and restore partitioned cookies. See [CHIPS MDN article](https://developer.mozilla.org/en-US/docs/Web/Privacy/Guides/Privacy_sandbox/Partitioned_cookies) 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. ```js import { defineConfig } from '@&#8203;playwright/test'; export default defineConfig({ reporter: [['html', { noSnippets: true }]] }); ``` - New property `location` in test annotations, for example in [testResult.annotations](https://playwright.dev/docs/api/class-testresult#test-result-annotations) and [testInfo.annotations](https://playwright.dev/docs/api/class-testinfo#test-info-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. ```bash 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`](https://github.com/microsoft/playwright/releases/tag/v1.53.2) [Compare Source](https://github.com/microsoft/playwright/compare/v1.53.1...v1.53.2) ##### Highlights https://github.com/microsoft/playwright/issues/36317 - \[Regression]: Merging pre-1.53 blob reports loses attachments https://github.com/microsoft/playwright/pull/36357 - \[Regression (Chromium)]: CDP missing trailing slash https://github.com/microsoft/playwright/issues/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`](https://github.com/microsoft/playwright/releases/tag/v1.53.1) [Compare Source](https://github.com/microsoft/playwright/compare/v1.53.0...v1.53.1) ##### Highlights https://github.com/microsoft/playwright/issues/36339 - \[Regression]: Click can fail when scrolling required https://github.com/microsoft/playwright/issues/36307 - \[Regression (Chromium)]: Under some scenarios filling a `textarea` doesn't fill https://github.com/microsoft/playwright/issues/36294 - \[Regression (Firefox)]: `setViewportSize` times out https://github.com/microsoft/playwright/pull/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`](https://github.com/microsoft/playwright/releases/tag/v1.53.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.52.0...v1.53.0) #### Trace Viewer and HTML Reporter Updates - New Steps in Trace Viewer and HTML reporter: <img src="https://github.com/user-attachments/assets/1963ff7d-4070-41be-a79b-4333176921a2" alt="New Trace Viewer Steps" height="500"> - New option in `'html'` reporter to set the title of a specific test run: ```js import { defineConfig } from '@&#8203;playwright/test'; export default defineConfig({ reporter: [['html', { title: 'Custom test run #&#8203;1028' }]] }); ``` #### Miscellaneous - New option [`kind`](https://playwright.dev/docs/api/class-testinfo#test-info-snapshot-path-option-kind) in [testInfo.snapshotPath()](https://playwright.dev/docs/api/class-testinfo#test-info-snapshot-path) controls which snapshot path template is used. - New method [locator.describe()](https://playwright.dev/docs/api/class-locator#locator-describe) to describe a locator. Used for trace viewer and reports. ```js 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`](https://github.com/microsoft/playwright/releases/tag/v1.52.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.51.1...v1.52.0) #### Highlights - New method [expect(locator).toContainClass()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-contain-class) to ergonomically assert individual class names on the element. ```ts await expect(page.getByRole('listitem', { name: 'Ship v1.52' })).toContainClass('done'); ``` - [Aria Snapshots](https://playwright.dev/docs/aria-snapshots) got two new properties: [`/children`](https://playwright.dev/docs/aria-snapshots#strict-matching) for strict matching and `/url` for links. ```ts await expect(locator).toMatchAriaSnapshot(` - list - /children: equal - listitem: Feature A - listitem: - link "Feature B": - /url: "https://playwright.dev" `); ``` #### Test Runner - New property [testProject.workers](https://playwright.dev/docs/api/class-testproject#test-project-workers) allows to specify the number of concurrent worker processes to use for a test project. The global limit of property [testConfig.workers](https://playwright.dev/docs/api/class-testconfig#test-config-workers) still applies. - New [testConfig.failOnFlakyTests](https://playwright.dev/docs/api/class-testconfig#test-config-fail-on-flaky-tests) 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](https://playwright.dev/docs/api/class-testresult#test-result-annotations) contains annotations for each test retry. #### Miscellaneous - New option [`maxRedirects`](https://playwright.dev/docs/api/class-apirequest#api-request-new-context-option-max-redirects) in [apiRequest.newContext()](https://playwright.dev/docs/api/class-apirequest#api-request-new-context) to control the maximum number of redirects. - HTML reporter now supports *NOT filtering* via `!@&#8203;my-tag` or `!my-file.spec.ts` or `!p:my-project`. #### Breaking Changes - Changes to glob URL patterns in methods like [page.route()](https://playwright.dev/docs/api/class-page#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()](https://playwright.dev/docs/api/class-route#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()](https://playwright.dev/docs/api/class-browsercontext#browser-context-add-cookies). - 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`](https://github.com/microsoft/playwright/releases/tag/v1.51.1) [Compare Source](https://github.com/microsoft/playwright/compare/v1.51.0...v1.51.1) ##### Highlights https://github.com/microsoft/playwright/issues/35093 - \[Regression]: TimeoutOverflowWarning: [`2149630`](https://github.com/microsoft/playwright/commit/2149630296).634 does not fit into a 32-bit signed integer https://github.com/microsoft/playwright/issues/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`](https://github.com/microsoft/playwright/releases/tag/v1.51.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.50.1...v1.51.0) #### StorageState for indexedDB - New option [`indexedDB`](https://playwright.dev/docs/api/class-browsercontext#browser-context-storage-state-option-indexed-db) for [browserContext.storageState()](https://playwright.dev/docs/api/class-browsercontext#browser-context-storage-state) allows to save and restore IndexedDB contents. Useful when your application uses [IndexedDB API](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API) to store authentication tokens, like Firebase Authentication. Here is an example following the [authentication guide](https://playwright.dev/docs/auth#basic-shared-account-in-all-tests): ```js // 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. ![Copy prompt](https://github.com/user-attachments/assets/f3654407-dd6d-4240-9845-0d96df2bf30a) #### Filter visible elements New option [`visible`](https://playwright.dev/docs/api/class-locator#locator-filter-option-visible) for [locator.filter()](https://playwright.dev/docs/api/class-locator#locator-filter) allows matching only visible elements. ```js // 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](https://playwright.dev/docs/api/class-testconfig#test-config-capture-git-info) to capture git information into [testConfig.metadata](https://playwright.dev/docs/api/class-testconfig#test-config-metadata). ```js // 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: ![Git information in the report](https://github.com/user-attachments/assets/f5b3f6f4-aa08-4a24-816c-7edf33ef0c37) #### Test Step improvements A new [TestStepInfo](https://playwright.dev/docs/api/class-teststepinfo) object is now available in test steps. You can add step attachments or skip the step under some conditions. ```js 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()](https://playwright.dev/docs/api/class-page#page-emulate-media) and [browser.newContext()](https://playwright.dev/docs/api/class-browser#browser-new-context) allows to emulate the `prefers-contrast` media feature. - New option [`failOnStatusCode`](https://playwright.dev/docs/api/class-apirequest#api-request-new-context-option-fail-on-status-code) makes all fetch requests made through the [APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext) throw on response codes other than 2xx and 3xx. - Assertion [expect(page).toHaveURL()](https://playwright.dev/docs/api/class-pageassertions#page-assertions-to-have-url) 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 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTUuMiIsInVwZGF0ZWRJblZlciI6IjM5LjI2NC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
kjuulh added 1 commit 2025-03-26 00:04:01 +01:00
chore(deps): update dependency @playwright/test to v1.51.1 404cde1800
kjuulh force-pushed renovate/playwright-monorepo from 404cde1800 to efa011c16d 2025-04-18 02:32:48 +02:00 Compare
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.51.1 to chore(deps): update dependency @playwright/test to v1.52.0 2025-04-18 02:32:48 +02:00
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.52.0 to chore(deps): update dependency @playwright/test to v1.53.0 2025-06-11 02:36:24 +02:00
kjuulh force-pushed renovate/playwright-monorepo from efa011c16d to cbad15de0f 2025-06-11 02:36:26 +02:00 Compare
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.53.0 to chore(deps): update dependency @playwright/test to v1.53.1 2025-06-19 02:33:15 +02:00
kjuulh force-pushed renovate/playwright-monorepo from cbad15de0f to d6dc6f33e6 2025-06-19 02:33:17 +02:00 Compare
kjuulh force-pushed renovate/playwright-monorepo from d6dc6f33e6 to e94c37d975 2025-07-01 02:37:05 +02:00 Compare
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.53.1 to chore(deps): update dependency @playwright/test to v1.53.2 2025-07-01 02:37:05 +02:00
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.53.2 to chore(deps): update dependency @playwright/test to v1.54.0 2025-07-11 02:37:06 +02:00
kjuulh force-pushed renovate/playwright-monorepo from e94c37d975 to c19784b41a 2025-07-11 02:37:08 +02:00 Compare
kjuulh force-pushed renovate/playwright-monorepo from c19784b41a to 0c0125af23 2025-07-12 02:33:44 +02:00 Compare
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.54.0 to chore(deps): update dependency @playwright/test to v1.54.1 2025-07-12 02:33:44 +02:00
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.54.1 to chore(deps): update dependency @playwright/test to v1.56.1 2025-11-13 03:14:27 +01:00
kjuulh force-pushed renovate/playwright-monorepo from 0c0125af23 to 7af7c4bd2d 2025-11-13 03:14:28 +01:00 Compare
kjuulh changed title from chore(deps): update dependency @playwright/test to v1.56.1 to chore(deps): update dependency @playwright/test to v1.57.0 2025-11-26 02:37:35 +01:00
kjuulh force-pushed renovate/playwright-monorepo from 7af7c4bd2d to 7ed8c7204c 2025-11-26 02:37:35 +01:00 Compare
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/playwright-monorepo:renovate/playwright-monorepo
git checkout renovate/playwright-monorepo
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
kjuulh
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kjuulh/lebusiness-client#8
No description provided.
Delete Branch "renovate/playwright-monorepo"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?