Open
Bug 1917540
Opened 10 months ago
Updated 1 month ago
[meta] Support WebDriver BiDi in Playwright
Categories
(Remote Protocol :: WebDriver BiDi, task)
Remote Protocol
WebDriver BiDi
Tracking
(Not tracked)
NEW
People
(Reporter: whimboo, Unassigned)
References
(Depends on 4 open bugs, Blocks 1 open bug, )
Details
(Keywords: meta)
User Story
Reference: https://github.com/microsoft/playwright/blob/main/tests/bidi/README.md Steps: * Clone Playwright: https://github.com/microsoft/playwright * Run `npm install` (or `npm run clean` before in case of errors during installation) * Run `npm run build` (as well each time you make modifications to the source) * Use `DEBUG="pw:browser"` to log the output of Firefox to the terminal console * Use `DEBUG="pw:protocol"` to log the usage of Juggler and CDP protocol to the terminal console * Use `PWDEBUGIMPL=1` to see a full stack of where the error was thrown * Use `PWTEST_FIREFOX_USER_PREFS='{"remote.log.level":"Trace"}'` to set custom Firefox preferences * Use `PWTEST_USE_BIDI_EXPECTATIONS=1` to enable custom expectations (e.g. skipping tests that timeout) * Use `BIDI_FFPATH=/%path%/%to%/%firefox%/%binary%` to use a custom build of Firefox * Use `CI=1` to get test results written to `test-results/report.json` * Run tests: `npm run biditest -- --project='bidi-firefox-%train%*' [%path%/%to%/%tests]` (train is one of `nightly`, `beta`, or `stable`) Further to run only individual tests you can also use `it.only` (that prevents requiring the path as mentioned above)
This bug tracks the required tasks and enhancements to WebDriver BiDi to ensure full compatibility with Playwright. It identifies the existing feature gaps and outlines the work needed to close them, allowing seamless integration of WebDriver BiDi with Playwright's functionality.
|
Reporter | |
Updated•10 months ago
|
|
|
Reporter | |
Updated•9 months ago
|
User Story: (updated)
|
|
Reporter | |
Comment 1•7 months ago
|
||
Trying to get Playwright tests and reporting correct results to the console I went through some issues. To help others to more easily run the tests I've put the required steps for running the tests into the user story field.
User Story: (updated)
|
|
Reporter | |
Updated•7 months ago
|
User Story: (updated)
|
|
Reporter | |
Updated•6 months ago
|
User Story: (updated)
|
|
Reporter | |
Updated•6 months ago
|
User Story: (updated)
|
|
Reporter | |
Updated•6 months ago
|
User Story: (updated)
|
|
Reporter | |
Updated•3 months ago
|
User Story: (updated)
|
|
Reporter | |
Updated•1 month ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•