Bump Microsoft.Playwright from 1.48.0 to 1.57.0 #60
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Microsoft.Playwright from 1.48.0 to 1.57.0.
Release notes
Sourced from Microsoft.Playwright's releases.
1.57.0
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.
Breaking Change
After 3 years of being deprecated, we removed
Page.Accessibilityfrom our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.New APIs
Stepsin Locator.ClickAsync() and Locator.DragToAsync() that configures the number ofmousemoveevents emitted while moving the mouse pointer to the target element.Browser Versions
1.56.0
New APIs
Breaking Changes
Miscellaneous
inputplaceholderBrowser Versions
1.55.0
Codegen
ToBeVisibleAsync()assertions: Codegen can now generate automaticToBeVisibleAsync()assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.Breaking Changes
Miscellaneous
Microsoft.Playwright.Xunit.v3Microsoft.Playwright.MSTest.v4Browser Versions
This version was also tested against the following stable channels:
1.54.0
Highlights
New cookie property
PartitionKeyin browserContext.cookies() and browserContext.addCookies(). This property allows to save and restore partitioned cookies. See CHIPS MDN article for more information. Note that browsers have different support and defaults for cookie partitioning.New option
--user-data-dirin multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.pwsh bin/Debug/netX/playwright.ps1 opendoes not open the test recorder anymore. Usepwsh bin/Debug/netX/playwright.ps1 codegeninstead.Browser Versions
This version was also tested against the following stable channels:
1.53.0
Miscellaneous
New Steps in Trace Viewer:

New method Locator.Describe() to describe a locator. Used for trace viewer.
pwsh bin/Debug/netX/playwright.ps1 install --listwill now list all installed browsers, versions and locations.Browser Versions
This version was also tested against the following stable channels:
1.52.0
Highlights
New method Expect(locator).ToContainClassAsync() to ergonomically assert individual class names on the element.
Aria Snapshots got two new properties:
/childrenfor strict matching and/urlfor links.Miscellaneous
MaxRedirectsin apiRequest.NewContextAsync() to control the maximum number of redirects.Refin locator.AriaSnapshotAsync() to generate reference for each element in the snapshot which can later be used to locate the element.Breaking Changes
Cookieheader anymore. If aCookieheader is provided, it will be ignored, and the cookie will be loaded from the browser's cookie store. To set custom cookies, use browserContext.AddCookiesAsync().Browser Versions
This version was also tested against the following stable channels:
1.51.0
Highlights
New option
IndexedDBfor BrowserContext.StorageStateAsync() allows to save and restore IndexedDB contents. Useful when your application uses IndexedDB API to store authentication tokens, like Firebase Authentication.Here is an example following the authentication guide:
New option
Visiblefor locator.filter() allows matching only visible elements.New option
Contrastfor methods page.emulateMedia() and Browser.NewContextAsync() allows to emulate theprefers-contrastmedia feature.New option
FailOnStatusCodemakes all fetch requests made through the APIRequestContext throw on response codes other than 2xx and 3xx.Browser Versions
This version was also tested against the following stable channels:
1.50.0
Support for Xunit
Miscellaneous
UI updates
canvascontent in traces is error-prone. Display is now disabled by default, and can be enabled via theDisplay canvas contentUI setting.CallandNetworkpanels now display additional time information.Breaking
<input>,<select>, or a number of other editable elements.Browser Versions
This version was also tested against the following stable channels:
1.49.0
Aria snapshots
New assertion Expect(locator).toMatchAriaSnapshot() verifies page structure by comparing to an expected accessibility tree, represented as YAML.
You can generate this assertion with Test Generator or by calling locator.ariaSnapshot().
Learn more in the aria snapshots guide.
Tracing groups
New method tracing.group() allows you to visually group actions in the trace viewer.
Breaking:
chromeandmsedgechannels switch to new headless modeThis change affects you if you're using one of the following channels in your
playwright.config.ts:chrome,chrome-dev,chrome-beta, orchrome-canarymsedge,msedge-dev,msedge-beta, ormsedge-canaryAfter 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.
Try new Chromium headless
You can opt into the new headless mode by using
'chromium'channel. As official Chrome documentation puts it: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.
... (truncated)
Commits viewable in compare view.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)