docs: 1.57 release notes#38267
Conversation
| 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 |
There was a problem hiding this comment.
I'm sorry to bother, but does this change anything related to #33566? / https://playwright.dev/docs/release-notes#try-new-chromium-headless ?
I don't know what I'm actually wanting to ask but does Playwright still provides this "old" Chromium Headless (1.48 figure/ --only-shell) or everything is using the new "new headless" (section "Opt-in to new headless
")?
Please ignore if this question if it doesn't make sense.
There was a problem hiding this comment.
Nothing changes in regards to headless shell, new headless and headed.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
| 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 |
There was a problem hiding this comment.
Nothing changes in regards to headless shell, new headless and headed.
| - [`method: Locator.description`] returns locator description previously set with [`method: Locator.describe`], and `Locator.toString()` now uses the description when available. | ||
| - New option [`option: Locator.click.steps`] in [`method: Locator.click`] and [`method: Locator.dragTo`] that configures the number of `mousemove` events emitted while moving the mouse pointer to the target element. | ||
| - [Service Worker network events](./service-workers.md#network-events-and-routing) are now reported to [BrowserContext](./api/class-browsercontext.md) and its routes. You can opt out using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK` environment variable. | ||
| - New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`]. |
There was a problem hiding this comment.
| - New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`]. |
| - New option [`option: Locator.click.steps`] in [`method: Locator.click`] and [`method: Locator.dragTo`] that configures the number of `mousemove` events emitted while moving the mouse pointer to the target element. | ||
| - [Service Worker network events](./service-workers.md#network-events-and-routing) are now reported to [BrowserContext](./api/class-browsercontext.md) and its routes. You can opt out using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK` environment variable. | ||
| - New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`]. | ||
| - Option [`property: TestConfig.webServer`] added a `wait` field to check readiness based on stdout/stderr. |
There was a problem hiding this comment.
| - Option [`property: TestConfig.webServer`] added a `wait` field to check readiness based on stdout/stderr. |
| }); | ||
| ``` | ||
|
|
||
| If your webserver runs on varying ports, use `wait` to capture the port: |
There was a problem hiding this comment.
This is good, but I think we should expand the webserver guide, link from this doc to the guide, and perhaps trim this doc instead.
Co-authored-by: Dmitry Gozman <dgozman@gmail.com> Signed-off-by: Simon Knott <info@simonknott.de>
Test results for "MCP"2 flaky2430 passed, 116 skipped Merge workflow run. |
Test results for "tests 1"5 flaky40316 passed, 787 skipped Merge workflow run. |
Signed-off-by: Simon Knott <info@simonknott.de> Co-authored-by: Dmitry Gozman <dgozman@gmail.com>
No description provided.