[Snyk] Upgrade @playwright/test from 1.19.0-alpha-1643749494000 to 1.38.1 #791
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @playwright/test from 1.19.0-alpha-1643749494000 to 1.38.1. See this package in npm: https://www.npmjs.com/package/@playwright/test See this project in Snyk: https://app.snyk.io/org/l00163425/project/81e8fe7d-ceaa-41cb-97a0-1afdb66407ba?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @playwright/test from 1.19.0-alpha-1643749494000 to 1.38.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version fixes:
SNYK-JS-BABELTRAVERSE-5962462
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
SNYK-JS-JPEGJS-2859218
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
SNYK-JS-SEMVER-3247795
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
SNYK-JS-JSON5-3182856
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
SNYK-JS-JSON5-3182856
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
SNYK-JS-MINIMATCH-3050818
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
SNYK-JS-MINIMIST-2429795
Why? Currently trending on Twitter, Recently disclosed, Has a fix available, CVSS 9.3
(*) Note that the real score may have changed since the PR was raised.
Release notes
Package name: @playwright/test
Highlights
#27071 - expect(value).toMatchSnapshot() deprecation announcement on V1.38
#27072 - [BUG] PWT trace viewer fails to load trace and throws TypeError
#27073 - [BUG] RangeError: Invalid time value
#27087 - [REGRESSION]: npx playwright test --list prints all tests twice
#27113 - [REGRESSION]: No longer able to extend PlaywrightTest.Matchers type for locators and pages
#27144 - [BUG]can not display trace
#27163 - [REGRESSION] Single Quote Wrongly Escaped by Locator When Using Unicode Flag
#27181 - [BUG] evaluate serializing fails at 1.38
Browser Versions
This version was also tested against the following stable channels:
UI Mode Updates
New APIs
browserContext.on('weberror')locator.pressSequentially()reporter.onEnd()now reportsstartTimeand total runduration.Deprecations
page.type(),frame.type(),locator.type()andelementHandle.type().Please use
locator.fill()instead which is much faster. Uselocator.pressSequentially()only if there is aspecial keyboard handling on the page, and you need to press keys one-by-one.
Breaking Changes: Playwright no longer downloads browsers automatically
Note
If you are using
@ playwright/testpackage, this change does not affect you.Playwright recommends to use
@ playwright/testpackage and download browsers vianpx playwright installcommand. If you are following this recommendation, nothing has changed for you.However, up to v1.38, installing the
playwrightpackage instead of@ playwright/testdid automatically download browsers. This is no longer the case, and we recommend to explicitly download browsers vianpx playwright installcommand.v1.37 and earlier
playwrightpackage was downloading browsers duringnpm install, while@ playwright/testwas not.v1.38 and later
playwrightand@ playwright/testpackages do not download browsers duringnpm install.Recommended migration
Run
npx playwright installto download browsers afternpm install. For example, in your CI configuration:Alternative migration option - not recommended
Add
@ playwright/browser-chromium,@ playwright/browser-firefoxand@ playwright/browser-webkitas a dependency. These packages download respective browsers duringnpm install. Make sure you keep the version of all playwright packages in sync:Browser Versions
This version was also tested against the following stable channels:
Highlights
#26496 - [REGRESSION] webServer stdout is always getting printed
#26492 - [REGRESSION] test.only with project dependency is not working
Browser Versions
This version was also tested against the following stable channels:
Watch the overview: Playwright 1.36 & 1.37
✨ New tool to merge reports
If you run tests on multiple shards, you can now merge all reports in a single HTML report (or any other report)
using the new
merge-reportsCLI tool.Using
merge-reportstool requires the following steps:Adding a new "blob" reporter to the config when running on CI:
The "blob" reporter will produce ".zip" files that contain all the information
about the test run.
Copying all "blob" reports in a single shared location and running
npx playwright merge-reports:Read more in our documentation.
📚 Debian 12 Bookworm Support
Playwright now supports Debian 12 Bookworm on both x86_64 and arm64 for Chromium, Firefox and WebKit.
Let us know if you encounter any issues!
Linux support looks like this:
🌈 UI Mode Updates
Browser Versions
This version was also tested against the following stable channels:
Highlights
#24316 - [REGRESSION] Character classes are not working in globs in 1.36
Browser Versions
This version was also tested against the following stable channels:
Highlights
#24184 - [REGRESSION]: Snapshot name contains some random string after test name when tests are run in container
Browser Versions
This version was also tested against the following stable channels:
Watch the overview: Playwright 1.36 & 1.37
Highlights
🏝️ Summer maintenance release.
Browser Versions
This version was also tested against the following stable channels:
Highlights
#23622 - [Docs] Provide a description how to correctly use expect.configure with poll parameter
#23666 - [BUG] Live Trace does not work with Codespaces
#23693 - [BUG] attachment steps are not hidden inside expect.toHaveScreenshot()
Browser Versions
This version was also tested against the following stable channels:
Playwright v1.35 updates
Highlights
UI mode is now available in VSCode Playwright extension via a new "Show trace viewer" button:
UI mode and trace viewer mark network requests handled with
page.route()andbrowserContext.route()handlers, as well as those issued via the API testing:New option
maskColorfor methodspage.screenshot(),locator.screenshot(),expect(page).toHaveScreenshot()andexpect(locator).toHaveScreenshot()to change default masking color:New
uninstallCLI command to uninstall browser binaries:Both UI mode and trace viewer now could be opened in a browser tab:
playwright-corebinary got renamed fromplaywrighttoplaywright-core. So if you useplaywright-coreCLI, make sure to update the name:$ npx playwright-core install # the new way to install browsers when using playwright-coreThis change does not affect
@ playwright/testandplaywrightpackage users.Browser Versions
This version was also tested against the following stable channels: