microsoft / microsoft/vscode-test-web
Make Playwright an optional dependency
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 87
- Forks
- 31
- Avg merge
- 23h 49m
- Merged PRs (30d)
- 5
Description
Howdy 👋
I am maintaining WebdriverIO and build a VS Code test plugin for it called wdio-vscode-service. It offers pretty much what @vscode/test-web and @vscode/test-electron do combined with a versatile test framework like WebdriverIO.
It would my life tremendously easier if this package could get rid of the Playwright dependency, which is only used to start up Chromium. There are other packages doing the same job using the actual Chrome browser installed on the system. It would also reduce installation time.
I am happy to make this change. It would allow me to use all the logic to spin up a VS Code server for testing web extensions.
Cheers!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where this package uses Playwright to start Chromium and review the package dependency configuration. Compare that startup path with the installed Chrome-based approach described in the issue. Done means Playwright is no longer required for installation while VS Code web-extension testing still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, playwright
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100