note: die Zusammenfassung und die Release Notes sind auf Englisch
note: keine Zusammenfassung für dieses ältere Release
Wir fassen die neueren Releases zusammen. Die originalen Release Notes dieser Version stehen hier unten.
release-notesgithub.com/microsoft/playwright · 69 Zeilen
- ## Speedboard
- In HTML reporter, there's a new tab we call "Speedboard":
- <img width="600" alt="speedboard" src="https://github.com/user-attachments/assets/4ba117ea-ea94-4b6a-82b2-8bbd00dfe81c" />
- 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](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.
- We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.
- <img width="500" alt="new and old logo" src="https://github.com/user-attachments/assets/e9a5c4f2-9f35-4c27-9382-0f5eda377097" />
- If you still see an unexpected behaviour change, please [file an issue](https://github.com/microsoft/playwright/issues/new).
- On Arm64 Linux, Playwright continues to use Chromium.
- ## Waiting for webserver output
- [testConfig.webServer](https://playwright.dev/docs/api/class-testconfig#test-config-web-server) added a `wait` field. Pass a regular expression, and Playwright will wait until the webserver logs match it.
- ```js
- import { defineConfig } from '@playwright/test';
- 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:
- ```js
- import { test, expect } from '@playwright/test';
- test.use({ baseUrl: `http://localhost:${process.env.MY_SERVER_PORT ?? 3000}` });
- 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#accessibility` from our API. Please use other libraries such as [Axe](https://www.deque.com/axe/) if you need to test page accessibility. See our Node.js [guide](https://playwright.dev/docs/accessibility-testing) for integration with Axe.
- ## New APIs
- - New property [testConfig.tag](https://playwright.dev/docs/api/class-testconfig#test-config-tag) adds a tag to all tests in this run. This is useful when using [merge-reports](https://playwright.dev/docs/test-sharding#merging-reports-from-multiple-shards).
- - [worker.on('console')](https://playwright.dev/docs/api/class-worker#worker-event-console) event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. [worker.waitForEvent()](https://playwright.dev/docs/api/class-worker#worker-wait-for-event) can be used to wait for it.
- - [locator.description()](https://playwright.dev/docs/api/class-locator#locator-description) returns locator description previously set with [locator.describe()](https://playwright.dev/docs/api/class-locator#locator-describe), and `Locator.toString()` now uses the description when available.
- - New option [`steps`](https://playwright.dev/docs/api/class-locator#locator-click-option-steps) in [locator.click()](https://playwright.dev/docs/api/class-locator#locator-click) and [locator.dragTo()](https://playwright.dev/docs/api/class-locator#locator-drag-to) that configures the number of `mousemove` events emitted while moving the mouse pointer to the target element.
- - Network requests issued by [Service Workers](https://playwright.dev/docs/service-workers#network-events-and-routing) are now reported and can be routed through the [BrowserContext](https://playwright.dev/docs/api/class-browsercontext), only in Chromium. You can opt out using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK` environment variable.
- - Console messages from Service Workers are dispatched through [worker.on('console')](https://playwright.dev/docs/api/class-worker#worker-event-console). You can opt out of this using the `PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE` environment variable.
- ## Browser Versions
- - Chromium 143.0.7499.4
- - Mozilla Firefox 144.0.2
- - WebKit 26.0