[Snyk] Upgrade playwright from 1.38.1 to 1.57.0 #17
Conversation
This file contains hidden or 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 from 1.38.1 to 1.57.0. See this package in npm: playwright See this project in Snyk: https://app.snyk.io/org/angeloreale/project/381e67e6-ce13-4593-8990-fb8e2248c688?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.
Snyk has created this PR to upgrade playwright from 1.38.1 to 1.57.0.
ℹ️ 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 is 1223 versions ahead of your current version.
The recommended version was released 23 days ago.
Release notes
Package name: playwright
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
waitfield. Pass a regular expression, and Playwright will wait until the webserver logs match it.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:
test.use({ baseUrl:
http://localhost:<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">process</span><span class="pl-kos">.</span><span class="pl-c1">env</span><span class="pl-kos">.</span><span class="pl-c1">MY_SERVER_PORT</span> <span class="pl-c1">??</span> <span class="pl-c1">3000</span><span class="pl-kos">}</span></span>});test('homepage', async ({ page }) => {
await page.goto('/');
});
This is not just useful for capturing varying ports of dev servers. You can also use it to wait for readiness of a service that doesn't expose an HTTP readiness check, but instead prints a readiness message to stdout or stderr.
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
Locator.toString()now uses the description when available.stepsin locator.click() and locator.dragTo() that configures the number ofmousemoveevents emitted while moving the mouse pointer to the target element.PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORKenvironment variable.PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLEenvironment variable.Browser Versions
Highlights
#37871 chore: allow local-network-access permission in chromium
#37891 fix(agents): remove workspaceFolder ref from vscode mcp
#37759 chore: rename agents to test agents
#37757 chore(mcp): fallback to cwd when resolving test config
Browser Versions
Playwright Agents
Introducing Playwright Agents, three custom agent definitions designed to guide LLMs through the core process of building a Playwright test:
Run
npx playwright init-agentswith your client of choice to generate the latest agent definitions:Note
VS Code v1.105 (currently on the VS Code Insiders channel) is needed for the agentic experience in VS Code. It will become stable shortly, we are a bit ahead of times with this functionality!
Learn more about Playwright Agents
New APIs
--test-listand--test-list-invertto allow manual specification of specific tests from a fileUI Mode and HTML Reporter
'html'reporter to disable the "Copy prompt" button'html'reporter and UI Mode to merge files, collapsing test and describe blocks into a single unified list--update-snapshotsoptionsBreaking Changes
Miscellaneous
inputplaceholderPLAYWRIGHT_TESTto Playwright worker processes to allow discriminating on testing statusBrowser Versions
Highlights
#37479 - [Bug]: Upgrade Chromium to 140.0.7339.186.
#37147 - [Regression]: Internal error: step id not found.
#37146 - [Regression]: HTML reporter displays a broken chip link when there are no projects.
#37137 - Revert "fix(a11y): track inert elements as hidden".
#37532 - chore: do not use -k option
Browser Versions
This version was also tested against the following stable channels:
New APIs
Codegen
toBeVisible()assertions: Codegen can now generate automatictoBeVisible()assertions for common UI interactions. This feature can be enabled in the Codegen settings UI.Breaking Changes
Miscellaneous
Browser Versions
This version was also tested against the following stable channels:
Highlights
#36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)
#36828 - [Regression]: Playwright Codegen keeps spamming with selected option
#36810 - [Regression]: Starting Codegen with target language doesn't work anymore
Browser Versions
This version was also tested against the following stable channels:
Highlights
#36650 - [Regression]: 1.54.0 breaks downloading browsers when an HTTP(S) proxy is used
Browser Versions
This version was also tested against the following stable channels:
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
noSnippetsto disable code snippets in the html report.export default defineConfig({
reporter: [['html', { noSnippets: true }]]
});
New property
locationin test annotations, for example in testResult.annotations and testInfo.annotations. It shows where the annotation liketest.skiportest.fixmewas added.Command Line
New option
--user-data-dirin multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.Option
-gvhas been removed from thenpx playwright testcommand. Use--grep-invertinstead.npx playwright opendoes not open the test recorder anymore. Usenpx playwright codegeninstead.Miscellaneous
Browser Versions
This version was also tested against the following stable channels:
Highlights
#36317 - [Regression]: Merging pre-1.53 blob reports loses attachments
#36357 - [Regression (Chromium)]: CDP missing trailing slash
#36292 - [Bug (MSEdge)]: Edge fails to launch when using
msRelaunchNoCompatLayerBrowser Versions
This version was also tested against the following stable channels:
Highlights
#36339 - [Regression]: Click can fail when scrolling required
#36307 - [Regression (Chromium)]: Under some scenarios filling a
textareadoesn't fill#36294 - [Regression (Firefox)]:
setViewportSizetimes out#36350 - [Fix]: Display HTTP method for fetch trace entries
Browser Versions
This version was also tested against the following stable channels: