Skip to content

test: allow running browser mode tests with docker playwright + add docs examples#9600

Merged
sheremet-va merged 13 commits intovitest-dev:mainfrom
hi-ogawa:docs-test-playwright-docker
Feb 8, 2026
Merged

test: allow running browser mode tests with docker playwright + add docs examples#9600
sheremet-va merged 13 commits intovitest-dev:mainfrom
hi-ogawa:docs-test-playwright-docker

Conversation

@hi-ogawa
Copy link
Copy Markdown
Collaborator

@hi-ogawa hi-ogawa commented Feb 6, 2026

Description

Related

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:.

@netlify
Copy link
Copy Markdown

netlify bot commented Feb 6, 2026

Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit f764629
🔍 Latest deploy log https://app.netlify.com/projects/vitest-dev/deploys/6986f9ce4df27300087259ca
😎 Deploy Preview https://deploy-preview-9600--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@hi-ogawa hi-ogawa changed the title docs: browser mode with docker playwright test: allow running browser mode test suites with docker playwright Feb 6, 2026
@hi-ogawa hi-ogawa changed the title test: allow running browser mode test suites with docker playwright test: allow running browser mode tests with docker playwright Feb 6, 2026
@hi-ogawa hi-ogawa self-assigned this Feb 7, 2026
hi-ogawa and others added 8 commits February 7, 2026 13:41
- Use collapsible details block instead of ### heading
- Frame connectOptions.wsEndpoint as general remote connection feature
- Replace network_mode: host (Linux-only) with port mapping + exposeNetwork
- Bump Playwright version to 1.58.1

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@hi-ogawa hi-ogawa changed the title test: allow running browser mode tests with docker playwright test: allow running browser mode tests with docker playwright + add docs examples Feb 7, 2026
@hi-ogawa hi-ogawa marked this pull request as ready for review February 7, 2026 08:46
@sheremet-va sheremet-va merged commit 136d6dd into vitest-dev:main Feb 8, 2026
16 checks passed
@hi-ogawa hi-ogawa deleted the docs-test-playwright-docker branch February 9, 2026 00:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants