Update dependency @playwright/test to v1.62.1 #58
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/playwright-test-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.61.1→1.62.1Release Notes
microsoft/playwright (@playwright/test)
v1.62.1Compare Source
Bug Fixes
v1.62.0Compare Source
🧱 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:
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
signaloption that takes anAbortSignal, letting you cancel long-running actions, navigations, waits, and assertions:Providing a signal does not disable the default timeout; pass
timeout: 0to disable it.🖼️ WebP screenshots
expect(page).toHaveScreenshot() and expect(locator).toHaveScreenshot() can now store snapshots in the WebP format — just give the snapshot a
.webpname:page.screenshot() and [locator.screenshot() (https://playwright.dev/docs/api/class-locator#locator-screenshot) also accept
webpas atype, where quality100(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:
🔁 Isolated retries
New testConfig.retryStrategy controls when failed tests are retried.
The default
'immediate'retries as soon as a worker is free;'isolated'runs all retries at the end, one by one in a single worker, to minimize interference with the rest of the suite:New APIs
Browser and Context
credentialsincludes the context's virtual WebAuthn Credentials (passkeys) in the storage state, so they can be persisted and re-seeded into later contexts.Actions
scrolloption ("auto"|"none") on actions to opt out of Playwright's automatic scroll-into-view.Network
Evaluation
Command line & MCP
playwright-cli, runnable vianpx playwright mcpandnpx playwright cli.Reporters
mergeFilesreporter option:Announcements
Browser Versions
This version was also tested against the following stable channels:
Configuration
📅 Schedule: (UTC)
🚦 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 this update again.
This PR has been generated by Renovate Bot.
⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
File name: tests/e2e/package-lock.json
Review: renovate
@playwright/test1.61.1 → 1.62.1Verdict: blockers — PR as-is will break e2e install and leaves Playwright versions out of sync with the documented contract.
Blockers
tests/e2e/package-lock.jsonnot updated — CI runsnpm --prefix='./tests/e2e' ci(tests/e2e/Jenkinsfile).package.jsonasks for1.62.1while the lockfile still pins1.61.1;npm ciwill fail on version mismatch.tests/e2e/Dockerfile, and@playwright/testto stay in lockstep. Still onmcr.microsoft.com/playwright:v1.61.1-jammy/@playwright/test@1.61.1in:tests/e2e/Jenkinsfile:14tests/e2e/Dockerfile:1and:7Bump those (and regenerate
tests/e2e/package-lock.json) to 1.62.1 in the same change, or land a coordinated Renovate PR that updates all of them together.Suggestions / nits
package.jsonbump itself is fine once companions match.CI fix (attempt 1)
Root cause (
nuxt-clients-e2e/jenkins@471571dd):Change (pushed
ebc3cba):tests/e2e/package-lock.jsonfor@playwright/test@1.62.1tests/e2e/Jenkinsfilepod image,tests/e2e/Dockerfile(FROM + global install), README note →v1.62.1-jammyJenkins: https://jenkins.primne.com/job/nuxt-clients-e2e/job/PR-58/1/
Review: LGTM
Verdict: no blockers — routine
@playwright/test1.61.1 → 1.62.1 bump with versions kept in sync.Blockers
None.
Notes
package.json, lockfile,Dockerfile(FROM+ globalnpm install),Jenkinsfilepod image, and README all land on 1.62.1 — matches the repo convention that image tag ≡@playwright/test.Suggestions / nits
engines.node: >=20for Playwright packages. Officialmcr.microsoft.com/playwright:v1.62.1-jammyis fine; local e2e on Node 18 would fail — expected from upstream, not a PR issue.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.
Review: LGTM (no blockers)
Renovate bump
@playwright/test1.61.1 → 1.62.1 with lockfile, Docker image, Jenkins pod image, and README kept in sync. No secrets, no app-layer changes, no broken contracts in the diff.Blockers
None.
Suggestions / nits
node: >=20for Playwright packages (was>=18). CI is fine (mcr.microsoft.com/playwright:v1.62.1-jammy). Local non-Docker runs need Node 20+.View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.