Description

Related

• Does Vitest browser mode support running the browser remotely (e.g. in Docker)? #9306
• WSL Windows browser support #9169

I investigated playwright docker and browser mode. I adjusted test/browser test suites to so I can test it with playwright docker (mostly to test webkit on my archlinux machine). The documentation is also added to mention this use case.

There are two cases test/browser/fixtures/inspect and test/browser/fixtures/insecure-context not working. I found inspect can actually work with remote playwright. I'll create a separate PR to fix things around connectOptions and launchOptions.

I'm not sure it's worth running wsEndpoint test cases as another CI matrix. It looks technically doable, but I'll figure that out and discuss separately later.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.