Bump @playwright/test from 1.61.1 to 1.62.0 in /tests/e2e in the minor-patch group across 1 directory

[dependabot]

Bumps the minor-patch group with 1 update in the /tests/e2e directory: @playwright/test.

Updates @playwright/test from 1.61.1 to 1.62.0

Release notes

Sourced from @​playwright/test's releases.

v1.62.0

🧱 New component testing model

Component testing moves to a stories and galleries model. A story wraps your component in one specific scenario — hard-coded props, mock data, providers — and a gallery page that you serve renders stories on demand. The new fixtures.mount() fixture navigates to the gallery, mounts a story by id, and returns a Locator scoped to the story's root element:

test('click should expand', async ({ mount }) => {
  const component = await mount('components/Expandable/Stateful');
  await component.getByRole('button').click();
  await expect(component.getByTestId('expanded')).toHaveValue('true');
});

Pass a story type as a template argument to type-check its props, and use update(props) / unmount() on the returned locator to re-render or tear down within a test.

🛑 Cancel operations with AbortSignal

Most operations and web-first assertions now accept a signal option that takes an AbortSignal, letting you cancel long-running actions, navigations, waits, and assertions:

const controller = new AbortController();
setTimeout(() => controller.abort(), 1000);
await page.getByRole('button', { name: 'Submit' }).click({ signal: controller.signal });
await expect(page.getByText('Done')).toBeVisible({ signal: controller.signal });

Providing a signal does not disable the default timeout; pass timeout: 0 to disable it.

🖼️ WebP screenshots

expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() can now store snapshots in the WebP format — just give the snapshot a .webp name:

// Visual comparisons store the golden snapshot as lossless WebP.
await expect(page).toHaveScreenshot('homepage.webp');
// Standalone screenshots can trade quality for size with lossy WebP.
await page.screenshot({ path: 'homepage.webp', quality: 50 });

page.screenshot() and [locator.screenshot() (https://playwright.dev/docs/api/class-locator#locator-screenshot) also accept webp as a type, where quality 100 (the default) is lossless and lower values use lossy compression.

🧩 Custom test filtering with Reporter.preprocess()

New reporter.preprocess() hook runs after the configuration is resolved and before reporter.onBegin(), letting a reporter mark individual tests as skipped, excluded, fixed, or failing through a TestRun object:

</tr></table> 

... (truncated)

Commits

• e3950d9 chore: mark v1.62.0 (#41981)
• f07e0f7 cherry-pick(#41940): docs: release notes for v1.62 (#41967)
• 05a306c cherry-pick(#41964): Revert "feat(routeFromHar): add interceptAPIRequests opt...
• 2934858 fix: correct pending navigation log spacing (#41949)
• 4b0cc99 fix(test): unflake screencast backpressure test on slow macOS runner (#41951)
• bbbae6d test: fixme WebSocket locale test in Chromium 150 (#41944)
• 15c4f55 fix(mcp): identify downloads explicitly (#41933)
• f5fa967 fix(network): request.postData() returns null for empty string body override ...
• 0edafe4 fix(mcp): launch the Chrome profile that has the extension installed (#41939)
• 244a1ff feat(firefox): roll to r1538 (#41938)
• Additional commits viewable in compare view

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔴 End-to-end tests break because the test browser image was not upgraded alongside the test tool

The end-to-end test tool is upgraded to a new version (@playwright/test "1.62.0" at tests/e2e/package.json:6) without upgrading the pinned browser image it runs inside, so the browsers bundled in the container no longer match the tool and the tests fail to launch a browser.

Impact: The end-to-end test tier fails in CI (and in the local container), blocking the build even though nothing in the app changed.

Version pin mismatch between npm package and Playwright Docker image

The e2e suite runs inside the pinned image mcr.microsoft.com/playwright:v1.61.1-noble (.devcontainer/Dockerfile:3, also referenced in tests/README.md:29 and CLAUDE.md:91), which ships browser builds matching Playwright 1.61.1. The Makefile target only runs npm ci then npx playwright test (Makefile:27-28, Makefile:46-47) and never runs npx playwright install, so no 1.62.0 browsers are downloaded. Playwright validates that installed browser revisions match the package version; with @playwright/test at 1.62.0 the expected browser revisions differ from those baked into the 1.61.1 image, causing browserType.launch: Executable doesn't exist failures. Per CLAUDE.md, CI runs make test inside this exact image, so a green run requires the image tag and npm package version to be bumped together (the same class of coupled-bump issue documented for vite/vitest). The Docker image tag in .devcontainer/Dockerfile and the references in tests/README.md/CLAUDE.md must be bumped to v1.62.0-noble in the same change.

Prompt for agents

Bumping @playwright/test to 1.62.0 in tests/e2e/package.json changes the browser revisions Playwright expects at runtime. The e2e tests run inside the pinned Docker image mcr.microsoft.com/playwright:v1.61.1-noble (.devcontainer/Dockerfile line 3), which ships browsers for Playwright 1.61.1, and the Makefile (targets at Makefile lines 27-28 and 46-47) never runs `npx playwright install` — it relies entirely on the image's pre-baked browsers. As a result the e2e tier will fail with 'Executable doesn't exist' because no 1.62.0 browsers are present. Fix by bumping the Docker base image tag in .devcontainer/Dockerfile to v1.62.0-noble in the same PR, and update the stale version references in tests/README.md (line 29) and CLAUDE.md (line 91) to match. Verify with a full container `make test` run.

---

Was this helpful? React with 👍 or 👎 to provide feedback.