build(deps-dev): bump @playwright/test from 1.52.0 to 1.57.0

[dependabot]

Bumps @playwright/test from 1.52.0 to 1.57.0.

Release notes

Sourced from @​playwright/test's releases.

v1.57.0

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 '@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 '@playwright/test';
test.use({ baseUrl: http://localhost:${process.env.MY_SERVER_PORT ?? 3000} });
test('homepage', async ({ page }) => {
await page.goto('/');
});
</tr></table>

... (truncated)

Commits

• 8058197 cherry-pick(#38328): docs: update 1.57 release notes
• 54818c5 chore: mark 1.57.0 (#38320)
• 414c4f5 cherry-pick(#38301): fix(android): dont pass "--disable-sync" (#38301)
• ae3da48 cherry-pick(#38124): feat(firefox): roll to latest firefox and firefox-beta (...
• 3756978 chore: fix lint warning about useEffect (#38285)
• 019900f chore: update browser_patches (#38286)
• 483b722 docs: 1.57 release notes (#38267)
• 46d5ea0 Revert "feat: add request.body async getters (#38179)" (#38281)
• 0778fcf chore: hide run-server command (#38277)
• bf6a60f chore: default to ubuntu 24.04 for unsupported distros (#38269)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​playwright/test since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---

Note

Upgrade @playwright/test to 1.57.0, updating Playwright dependencies and lockfile accordingly.

^{Written by Cursor Bugbot for commit 893a0e6. This will update automatically on new commits. Configure here.}

[netlify]

✅ Deploy Preview for content-scope-scripts canceled.

Name	Link
🔨 Latest commit	893a0e6
🔍 Latest deploy log	https://app.netlify.com/projects/content-scope-scripts/deploys/6936e3f7428436000873dd39

[github-actions]

Temporary Branch Update

The temporary branch has been updated with the latest changes. Below are the details:

• Branch Name: pr-releases/pr-2069
• Commit Hash: 5171c6fb835e45a7d444651b3059af8b2dcb1e0a
• Last Updated: December 8, 2025 at 2:43:42 PM UTC
• Install Command: npm i github:duckduckgo/content-scope-scripts#5171c6fb835e45a7d444651b3059af8b2dcb1e0a

Please use the above install command to update to the latest version.

[jonathanKingston]

@dependabot rebase

[jonathanKingston]

@cursoragent can you review against our current workflows and outline potential impacts based on the changelogs of the update?

[cursor]

Playwright 1.52.0 → 1.57.0 Impact Analysis

Key Changes and Workflow Impact

1. Chrome for Testing Switch (v1.57.0) — HIGH IMPACT

The biggest change: Playwright now uses Chrome for Testing instead of Chromium.

Affected workflows:

• tests.yml (integration job on ubuntu-latest) — Uses Desktop Chrome
• snapshots.yml / snapshots-update.yml on macos-14 — Exception: Arm64 macOS continues using Chromium

Projects affected in configs:

            use: {
                ...devices['Desktop Chrome'],
                injectName: 'integration',
                platform: 'windows',
            },

            use: { injectName: 'chrome-mv3', platform: 'extension', ...devices['Desktop Chrome'] },

Expected Impact:

• Screenshot snapshots may need updating due to subtle rendering differences
• The cache at ~/.cache/ms-playwright will be invalidated (new lockfile hash) — new browsers will download automatically
• macOS-14 snapshot tests should be unaffected (Arm64 → still Chromium)

2. Cache Handling — LOW RISK

Your workflows correctly cache based on package-lock.json:

                      ~/.cache/ms-playwright
                  key: ${{ runner.os }}-node-playwright-${{ hashFiles('**/package-lock.json') }}

Cache invalidation will happen automatically with the lockfile change ✓

3. webServer Configuration — NO IMPACT

New wait field is opt-in. Your existing configs don't use it and will continue working:

    webServer: {
        reuseExistingServer: true,
        ignoreHTTPSErrors: true,
        command: 'npm run bundle-entry-points && npm run serve',
        port: 3220,
    },

4. HTML Reporter Speedboard — INFO ONLY

New "Speedboard" tab in HTML reports. No action needed — it's additive.

Risk Assessment

Area	Risk	Notes
Integration tests (ubuntu-latest)	Medium	Chrome for Testing may have different behavior
Screenshot tests (macos-14)	Low	Arm64 macOS still uses Chromium
Browser download time	Low	One-time cache rebuild
API compatibility	Low	No breaking API changes in this range

Recommended Actions

1. Merge and monitor — The upgrade is low-risk overall
2. If screenshot tests fail, run the snapshots-update.yml workflow to regenerate baselines
3. Verify CI passes — Watch the first run for any Chrome for Testing behavioral changes

Alternative

If concerned about snapshot stability, you could pin to 1.56.x first (no Chrome for Testing change), then upgrade to 1.57.x separately to isolate any snapshot issues.

---

 

_{Learn more about Cursor Agents}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}