chore(deps-dev): bump @playwright/test from 1.45.3 to 1.46.0

[dependabot[bot]]

Bumps @playwright/test from 1.45.3 to 1.46.0.

Release notes

Sourced from @​playwright/test's releases.

v1.46.0

TLS Client Certificates

Playwright now allows to supply client-side certificates, so that server can verify them, as specified by TLS Client Authentication.

When client certificates are specified, all browser traffic is routed through a proxy that establishes the secure TLS connection, provides client certificates to the server and validates server certificates.

The following snippet sets up a client certificate for https://example.com:

import { defineConfig } from '@playwright/test';
export default defineConfig({

// ...

use: {

clientCertificates: [{

origin: 'https://example.com',

certPath: './cert.pem',

keyPath: './key.pem',

passphrase: 'mysecretpassword',

}],

},

// ...

});

You can also provide client certificates to a particular test project or as a parameter of browser.newContext() and apiRequest.newContext().

--only-changed cli option

New CLI option --only-changed allows to only run test files that have been changed since the last git commit or from a specific git "ref".

# Only run test files with uncommitted changes
npx playwright test --only-changed
Only run test files changed relative to the "main" branch
npx playwright test --only-changed=main

Component Testing: New router fixture

This release introduces an experimental router fixture to intercept and handle network requests in component testing. There are two ways to use the router fixture:

• Call router.route(url, handler) that behaves similarly to page.route().
• Call router.use(handlers) and pass MSW library request handlers to it.

Here is an example of reusing your existing MSW handlers in the test.

</tr></table> 

... (truncated)

Commits

• 99a3631 chore: mark v1.46 (#32013)
• 929fef3 cherry-pick(#32012): chore(lint): bump Microsoft.CodeAnalysis for linting cod...
• cf31aa8 cherry-pick(#32008): chore(client-certificates): rewrite error for unsupporte...
• ed9b4d9 cherry-pick(#32007): fix(client-certificates): report error to the browser if...
• fca1fa0 cherry-pick(#31973): chore: run client-certificate tests in service mode
• ff11273 cherry-pick(#32010): docs: release notes for 1.46 update
• 4953ac3 cherry-pick(#31975): chore: remove bright counter from sidebar tab se… (#31976)
• 4c66f8a cherry-pick(#31970): fix(trace): do not place expect into unfinished … (#31974)
• deba37b cherry-pick(#31960): feat(ui mode): linkify attachment names and content (#31...
• 2cfe733 cherry-pick(#31961): fix(trace-viewer): make 'hide route actions' work for .NET
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)