examples/vue-ts-example-2025
1
0
Fork 0
Code Issues 1 Pull Requests 9 Actions Packages Projects Releases Wiki Activity

chore(deps): update dependency @playwright/test to v1.57.0 #150

Merged
gitea_1-h.cc merged 1 commits from renovate/playwright into main 2025-12-11 21:03:49 +08:00
Conversation 0 Commits 1 Files Changed 1 +12 -12
renovatebot commented 2025-11-28 21:23:20 +08:00
Collaborator
Copy Link

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@playwright/test (source) 1.56.1 -> 1.57.0 age adoption passing confidence

Release Notes

microsoft/playwright (@​playwright/test)

v1.57.0

Compare Source

Speedboard

In HTML reporter, there's a new tab we call "Speedboard":

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.

new and old logo

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 wait field. Pass a regular expression, and Playwright will wait until the webserver logs match it.

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:

import { test, expect } from '@&#8203;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 if you need to test page accessibility. See our Node.js guide for integration with Axe.

New APIs

  • New property testConfig.tag adds a tag to all tests in this run. This is useful when using merge-reports.
  • worker.on('console') event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. worker.waitForEvent() can be used to wait for it.
  • locator.description() returns locator description previously set with locator.describe(), and Locator.toString() now uses the description when available.
  • New option steps in locator.click() and locator.dragTo() that configures the number of mousemove events emitted while moving the mouse pointer to the target element.
  • Network requests issued by Service Workers are now reported and can be routed through the 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'). 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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Adoption](https://docs.renovatebot.com/merge-confidence/) | [Passing](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---|---|---| | [@playwright/test](https://playwright.dev) ([source](https://github.com/microsoft/playwright)) | [`1.56.1` -> `1.57.0`](https://renovatebot.com/diffs/npm/@playwright%2ftest/1.56.1/1.57.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@playwright%2ftest/1.57.0?slim=true) | ![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/@playwright%2ftest/1.57.0?slim=true) | ![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/@playwright%2ftest/1.56.1/1.57.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@playwright%2ftest/1.56.1/1.57.0?slim=true) | --- ### Release Notes <details> <summary>microsoft/playwright (@&#8203;playwright/test)</summary> ### [`v1.57.0`](https://github.com/microsoft/playwright/releases/tag/v1.57.0) [Compare Source](https://github.com/microsoft/playwright/compare/v1.56.1...v1.57.0) #### 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 '@&#8203;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 '@&#8203;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 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0Mi4yNi4yIiwidXBkYXRlZEluVmVyIjoiNDIuMjYuOSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
renovatebot force-pushed renovate/playwright from 47eee7d3b3 to 3a9d94d2ba 2025-11-30 14:48:19 +08:00 Compare
renovatebot force-pushed renovate/playwright from 3a9d94d2ba to 8a103919f3 2025-12-01 03:34:00 +08:00 Compare
renovatebot force-pushed renovate/playwright from 8a103919f3 to addfa5aee0 2025-12-02 00:34:58 +08:00 Compare
renovatebot force-pushed renovate/playwright from addfa5aee0 to bc329121bb 2025-12-04 17:38:20 +08:00 Compare
renovatebot force-pushed renovate/playwright from bc329121bb to b6ff02b9f4 2025-12-07 08:33:30 +08:00 Compare
renovatebot force-pushed renovate/playwright from b6ff02b9f4 to 0e440655c3 2025-12-07 19:34:20 +08:00 Compare
renovatebot force-pushed renovate/playwright from 0e440655c3 to 2d54d87dfc 2025-12-08 06:00:23 +08:00 Compare
renovatebot force-pushed renovate/playwright from 2d54d87dfc to b6b5d85ad6 2025-12-08 17:49:09 +08:00 Compare
renovatebot force-pushed renovate/playwright from b6b5d85ad6 to c6081de524 2025-12-08 23:41:30 +08:00 Compare
renovatebot force-pushed renovate/playwright from c6081de524 to 5e69932aee 2025-12-09 07:35:56 +08:00 Compare
renovatebot force-pushed renovate/playwright from 5e69932aee to f5309680dc 2025-12-10 02:30:54 +08:00 Compare
renovatebot force-pushed renovate/playwright from f5309680dc to 8c86248943 2025-12-10 17:06:29 +08:00 Compare
renovatebot force-pushed renovate/playwright from 8c86248943 to 4a7ad80c1f 2025-12-11 01:04:12 +08:00 Compare
renovatebot force-pushed renovate/playwright from 4a7ad80c1f to 55f34018be 2025-12-11 03:48:35 +08:00 Compare
renovatebot force-pushed renovate/playwright from 55f34018be to 29511eed21 2025-12-11 15:06:12 +08:00 Compare
renovatebot force-pushed renovate/playwright from 29511eed21 to 8669456749 2025-12-11 17:41:46 +08:00 Compare
renovatebot force-pushed renovate/playwright from 8669456749 to 8c77314161 2025-12-11 20:43:28 +08:00 Compare
gitea_1-h.cc merged commit 40b3686f2e into main 2025-12-11 21:03:49 +08:00
gitea_1-h.cc deleted branch renovate/playwright 2025-12-11 21:03:49 +08:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea_1-h.cc renovatebot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: examples/vue-ts-example-2025#150
Delete Branch "renovate/playwright"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?