fix(deps): update dependency @playwright/test to ^1.49.1

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
@playwright/test (source)	dependencies	minor	^1.47.2 -> ^1.49.1

---

Release Notes

microsoft/playwright (@​playwright/test)

v1.49.1

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/33802 - [Bug]: Codegen's Clear button doesn't work if not recordinghttps://github.com/microsoft/playwright/issues/338066 - [Bug]: playwright hangs while waiting for pending navigationhttps://github.com/microsoft/playwright/issues/3378787 - [Bug]: VSC extension isn't capturing all entered tehttps://github.com/microsoft/playwright/issues/33788788 - [Regression]: Double clicking the steps in trace viewer doesn't filter actihttps://github.com/microsoft/playwright/issues/337723772 - [Bug]: aria_snapshot generates invalid yaml when combined with an aria-label attrhttps://github.com/microsoft/playwright/issues/3379133791 - [Bug]: text input with number value raises "container is not iterable" with to_match_aria_snahttps://github.com/microsoft/playwright/issues/33644/33644 - [Bug]: getByRole can't find element with the accessible name from label element when aria-labelledby is nothttps://github.com/microsoft/playwright/issues/33660s/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 '@​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

https://github.com/microsoft/playwright/issues/33141 - [Bug]: UI Mode crashedhttps://github.com/microsoft/playwright/issues/332199 - [BUG] Trace Viewer PWA crashes with "Aw, Snap86 - [Bug]: UI Mode Memory problhttps://github.com/microsoft/playwright/issues/33000000 - [Regression]: Inspector and Browser doesn't close on CTRhttps://github.com/microsoft/playwright/issues/332043204 - [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

https://github.com/microsoft/playwright/issues/33023 - [Bug]: command line flag --headed has no effect in ui modehttps://github.com/microsoft/playwright/issues/331077 - [REGRESSION]: page.waitForRequest does not get resolved since 1.48.https://github.com/microsoft/playwright/issues/3308585 - [Bug]: WebSocket route does not handle full URLs in Playwrighttps://github.com/microsoft/playwright/issues/33052052 - [Regression]: Inspector not showing recorded sthttps://github.com/microsoft/playwright/issues/331323132 - [Bug]: Wrong Ubuntu release name in Dockerfile.nhttps://github.com/microsoft/playwright/pull/3299632996 - [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

---

Configuration

📅 Schedule: Branch creation - "every 2 weeks on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, 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.

[elastic-renovate-prod]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[elastic-datavis]

✅ Successful Preliminary Deployment (build#4323) - 650912e

• Docs
• Storybook
• e2e server
• ⏳ Playwright report - Running e2e tests