Commit fc59082
authored
fix(deps): Update dependency @playwright/test to v1.49.0 (#19737)
This PR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| [@playwright/test](https://playwright.dev) ([source](https://togithub.com/microsoft/playwright)) | devDependencies | minor | [`1.46.1` -> `1.49.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.46.1/1.49.0) |
| [@playwright/test](https://playwright.dev) ([source](https://togithub.com/microsoft/playwright)) | devDependencies | minor | [`1.48.0` -> `1.49.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.48.0/1.49.0) |
| [@playwright/test](https://playwright.dev) ([source](https://togithub.com/microsoft/playwright)) | devDependencies | minor | [`1.47.2` -> `1.49.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.47.2/1.49.0) |
---
> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
---
### Release Notes
<details>
<summary>microsoft/playwright (@​playwright/test)</summary>
### [`v1.49.0`](https://togithub.com/microsoft/playwright/releases/tag/v1.49.0)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.48.2...v1.49.0)
##### Aria snapshots
New assertion [expect(locator).toMatchAriaSnapshot()](https://playwright.dev/docs/api/class-locatorassertions#locator-assertions-to-match-aria-snapshot) verifies page structure by comparing to an expected accessibility tree, represented as YAML.
```js
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](https://playwright.dev/docs/codegen) and update the expected snapshot with `--update-snapshots` command line flag.
Learn more in the [aria snapshots guide](https://playwright.dev/docs/aria-snapshots).
##### Test runner
- New option [testConfig.tsconfig](https://playwright.dev/docs/api/class-testconfig#test-config-tsconfig) allows to specify a single `tsconfig` to be used for all tests.
- New method [test.fail.only()](https://playwright.dev/docs/api/class-test#test-fail-only) to focus on a failing test.
- Options [testConfig.globalSetup](https://playwright.dev/docs/api/class-testconfig#test-config-global-setup) and [testConfig.globalTeardown](https://playwright.dev/docs/api/class-testconfig#test-config-global-teardown) now support multiple setups/teardowns.
- New value `'on-first-failure'` for [testOptions.screenshot](https://playwright.dev/docs/api/class-testoptions#test-options-screenshot).
- Added "previous" and "next" buttons to the HTML report to quickly switch between test cases.
- New properties [testInfoError.cause](https://playwright.dev/docs/api/class-testinfoerror#test-info-error-cause) and [testError.cause](https://playwright.dev/docs/api/class-testerror#test-error-cause) mirroring [`Error.cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/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](https://togithub.com/microsoft/playwright/issues/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](https://developer.chrome.com/blog/chrome-headless-shell):
> 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](https://togithub.com/microsoft/playwright/issues/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.
```js
import { defineConfig, devices } from '@​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()](https://playwright.dev/docs/api/class-tracing#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`](https://togithub.com/microsoft/playwright/releases/tag/v1.48.2)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.48.1...v1.48.2)
##### Highlights
[https://github.com/microsoft/playwright/issues/33141](https://togithub.com/microsoft/playwright/issues/33141) - \[Bug]: UI Mode crashed[https://github.com/microsoft/playwright/issues/33219](https://togithub.com/microsoft/playwright/issues/33219)9 - \[BUG] Trace Viewer PWA crashes with "Aw, Snap86 - \[Bug]: UI Mode Memory probl[https://github.com/microsoft/playwright/issues/33000](https://togithub.com/microsoft/playwright/issues/33000)000 - \[Regression]: Inspector and Browser doesn't close on CTR[https://github.com/microsoft/playwright/issues/33204](https://togithub.com/microsoft/playwright/issues/33204)3204 - \[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`](https://togithub.com/microsoft/playwright/releases/tag/v1.48.1)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.48.0...v1.48.1)
##### Highlights
[https://github.com/microsoft/playwright/issues/33023](https://togithub.com/microsoft/playwright/issues/33023) - \[Bug]: command line flag --headed has no effect in ui mode[https://github.com/microsoft/playwright/issues/33107](https://togithub.com/microsoft/playwright/issues/33107)7 - \[REGRESSION]: page.waitForRequest does not get resolved since 1.48.[https://github.com/microsoft/playwright/issues/33085](https://togithub.com/microsoft/playwright/issues/33085)85 - \[Bug]: WebSocket route does not handle full URLs in Playwrig[https://github.com/microsoft/playwright/issues/33052](https://togithub.com/microsoft/playwright/issues/33052)052 - \[Regression]: Inspector not showing recorded st[https://github.com/microsoft/playwright/issues/33132](https://togithub.com/microsoft/playwright/issues/33132)3132 - \[Bug]: Wrong Ubuntu release name in Dockerfile.n[https://github.com/microsoft/playwright/pull/32996](https://togithub.com/microsoft/playwright/pull/32996)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`](https://togithub.com/microsoft/playwright/releases/tag/v1.48.0)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.47.2...v1.48.0)
##### WebSocket routing
New methods [page.routeWebSocket()](https://playwright.dev/docs/api/class-page#page-route-web-socket) and [browserContext.routeWebSocket()](https://playwright.dev/docs/api/class-browsercontext#browser-context-route-web-socket) 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"`.
```js
await page.routeWebSocket('/ws', ws => {
ws.onMessage(message => {
if (message === 'request')
ws.send('response');
});
});
```
See [WebSocketRoute](https://playwright.dev/docs/api/class-websocketroute) for more details.
##### UI updates
- New "copy" buttons for annotations and test location in the HTML report.
- Route method calls like [route.fulfill()](https://playwright.dev/docs/api/class-route#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`](https://playwright.dev/docs/api/class-apirequestcontext#api-request-context-fetch-option-form) and similar ones now accept [FormData](https://playwright.dev/docs/api/class-formdata).
- New method [page.requestGC()](https://playwright.dev/docs/api/class-page#page-request-gc) may help detect memory leaks.
- New option [`location`](https://playwright.dev/docs/api/class-test#test-step-option-location) to pass custom step location.
- Requests made by [APIRequestContext](https://playwright.dev/docs/api/class-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`](https://togithub.com/microsoft/playwright/releases/tag/v1.47.2)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.47.1...v1.47.2)
##### Highlights
[https://github.com/microsoft/playwright/pull/32699](https://togithub.com/microsoft/playwright/pull/32699)- \[REGRESSION]: fix(codegen): use content_frame property in python/.NET[https://github.com/microsoft/playwright/issues/32706](https://togithub.com/microsoft/playwright/issues/32706)6- \[REGRESSION]: page.pause() does not pause test timeout after 1.4[https://github.com/microsoft/playwright/pull/32661](https://togithub.com/microsoft/playwright/pull/32661)61 - 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`](https://togithub.com/microsoft/playwright/releases/tag/v1.47.1)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.47.0...v1.47.1)
##### Highlights
[https://github.com/microsoft/playwright/issues/32480](https://togithub.com/microsoft/playwright/issues/32480) - \[REGRESSION]: tsconfig.json's compilerOptions.paths no longer working in 1.47[https://github.com/microsoft/playwright/issues/32552](https://togithub.com/microsoft/playwright/issues/32552)2 - \[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`](https://togithub.com/microsoft/playwright/releases/tag/v1.47.0)
[Compare Source](https://togithub.com/microsoft/playwright/compare/v1.46.1...v1.47.0)
#### 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](https://togithub.com/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:
```sh
### Pass a specific tsconfig
npx playwright test --tsconfig tsconfig.test.json
```
#### [APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext) now accepts [`URLSearchParams`](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams) and `string` as query parameters
You can now pass [`URLSearchParams`](https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams) and `string` as query parameters to [APIRequestContext](https://playwright.dev/docs/api/class-apirequestcontext):
```ts
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()](https://playwright.dev/docs/api/class-page#page-remove-all-listeners), [browser.removeAllListeners()](https://playwright.dev/docs/api/class-browser#browser-remove-all-listeners) and [browserContext.removeAllListeners()](https://playwright.dev/docs/api/class-browsercontext#browser-context-remove-all-listeners) 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()](https://playwright.dev/docs/api/class-locator#locator-select-option) 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
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about these updates again.
---
- [ ] If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate).1 parent 504dc2c commit fc59082
7 files changed
Lines changed: 80 additions & 77 deletions
File tree
- plugins
- destination
- bigquery/cloud-config-ui
- clickhouse/cloud-config-ui
- mysql/cloud-config-ui
- postgresql/cloud-config-ui
- s3/cloud-config-ui
- source
- hackernews/cloud-config-ui
- xkcd/cloud-config-ui
Lines changed: 11 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 11 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 11 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 11 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 14 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Lines changed: 11 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments