Update dependency @playwright/test to v1.49.0

[openverse-bot]

This PR contains the following updates:

Package	Type	Update	Change
@playwright/test (source)	devDependencies	minor	1.48.2 -> 1.49.0

---

Release Notes

microsoft/playwright (@​playwright/test)

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

---

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), 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.

[github-actions]

Latest k6 run output¹

     ✓ status was 200

     checks.........................: 100.00% ✓ 6400      ✗ 0   
     data_received..................: 1.5 GB  8.3 MB/s
     data_sent......................: 838 kB  4.6 kB/s
     http_req_blocked...............: avg=12.89µs  min=2.05µs  med=3.71µs   max=7.47ms  p(90)=5.22µs   p(95)=5.64µs  
     http_req_connecting............: avg=8.77µs   min=0s      med=0s       max=7.43ms  p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=627.35ms min=70.05ms med=542.72ms max=2.72s   p(90)=1.13s    p(95)=1.24s   
       { expected_response:true }...: avg=627.35ms min=70.05ms med=542.72ms max=2.72s   p(90)=1.13s    p(95)=1.24s   
   ✓ http_req_failed................: 0.00%   ✓ 0         ✗ 6400
     http_req_receiving.............: avg=136.91µs min=41.29µs med=109.24µs max=18.51ms p(90)=172.41µs p(95)=210.49µs
     http_req_sending...............: avg=20.14µs  min=5.67µs  med=18.45µs  max=2.52ms  p(90)=23.9µs   p(95)=26.32µs 
     http_req_tls_handshaking.......: avg=0s       min=0s      med=0s       max=0s      p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=627.19ms min=69.92ms med=542.62ms max=2.72s   p(90)=1.13s    p(95)=1.24s   
     http_reqs......................: 6400    35.455183/s
     iteration_duration.............: avg=3.35s    min=1.14s   med=2.83s    max=9.54s   p(90)=6.55s    p(95)=6.9s    
     iterations.....................: 1200    6.647847/s
     vus............................: 9       min=9       max=30
     vus_max........................: 30      min=30      max=30

Footnotes

1. This comment will automatically update with new output each time k6 runs for this PR ↩

[github-actions]

Playwright failure test results: https://github.com/WordPress/openverse/actions/runs/12068634327

It looks like some of the Playwright tests failed. If you made changes to the frontend UI without updating snapshots, this might be the cause. You can download zipped patches containing the updated snapshots alongside a general trace of the tests under the "Artifacts" section in the above page. They're named in the form *_snapshot_diff and *_test_results respectively.

You can read more on how to use these artifacts in the docs.

If the test is flaky, follow the flaky test triage procedure.

[obulat]

Closing to recreate this PR - otherwise, would need to manually resolve pnpm-lock.yaml conflicts.

[openverse-bot]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (1.49.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.