You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/release-notes-js.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,13 @@ In HTML reporter, there's a new tab we call "Speedboard":
16
16
17
17
It shows you all your executed tests sorted by slowness,
18
18
and can help you understand where your test suite is taking longer than expected.
19
-
Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should!
19
+
Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should!
20
20
21
21
### Chrome for Testing
22
22
23
-
Starting with this release, Playwright switches from Chromium, to using [Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) builds.
24
-
Both headed and headless browsers are subject to this.
25
-
Your tests should still be passing after upgrading to Playwright 1.57.
26
-
We're expecting no functional changes to come from this switch - the biggest change is the new icon and title in your toolbar:
23
+
Starting with this release, Playwright switches from Chromium, to using [Chrome for Testing](https://developer.chrome.com/blog/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.
24
+
25
+
We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.
This is not just useful for capturing varying ports of dev servers:
64
-
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.
62
+
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.
65
63
66
64
### Breaking Change
67
65
@@ -70,12 +68,11 @@ After 3 years of being deprecated, we removed `Page#accessibility` from our API.
70
68
### New APIs
71
69
72
70
- New property [`property: TestConfig.tag`] adds a tag to all tests in this run. This is useful when using [merge-reports](./test-sharding.md#merging-reports-from-multiple-shards).
73
-
- [`event: Worker.console`] event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. [`method: Worker.waitForEvent`] can be used to wait for it. You can opt out of this using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE` environment variable.
71
+
- [`event: Worker.console`] event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. [`method: Worker.waitForEvent`] can be used to wait for it.
74
72
- [`method: Locator.description`] returns locator description previously set with [`method: Locator.describe`], and `Locator.toString()` now uses the description when available.
75
-
- 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.
73
+
- 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.
76
74
- Network requests issued by [Service Workers](./service-workers.md#network-events-and-routing) are now reported and can be routed through the [BrowserContext](./api/class-browsercontext.md), only in Chromium. You can opt out using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK` environment variable.
77
-
- New methods [`method: Request.postData`], [`method: Request.postDataBuffer`] and [`method: Request.postDataJSON`].
78
-
- Option [`property: TestConfig.webServer`] added a `wait` field to check readiness based on stdout/stderr.
75
+
- Console messages from Service Workers are dispatched through [`event: Worker.console`]. You can opt out of this using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE` environment variable.
0 commit comments