Update bugzilla component for WebDriver BiDi and CDP related files under web-platform-tests to "Remote Protocol / WebDriver BiDi"
Categories
(Remote Protocol :: Agent, task, P1)
Tracking
(firefox107 fixed)
| Tracking | Status | |
|---|---|---|
| firefox107 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [webdriver:m5])
Attachments
(1 file)
Right now this folder is still listed for Testing / Geckodriver but it has nothing to do with the WebDriver classic tests:
mach file-info bugzilla-component testing/web-platform/tests/webdriver/tests/bidi/
Testing :: geckodriver
testing/web-platform/tests/webdriver/tests/bidi/
Instead it should be listed as Remote Protocol / WebDriver BiDi.
Hereby we most likely should also add testing/web-platform/mozilla/tests/webdriver/bidi/ as well, and testing/web-platform/mozilla/tests/webdriver/cdp/ to Remote Protocol / CDP.
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Comment 1•2 years ago
|
||
|
||
Updated•2 years ago
|
|
|
Assignee | |
Comment 2•2 years ago
|
||
Setting as 1 point given that it's an easy fix.
|
|
Assignee | |
Comment 3•2 years ago
|
||
During the review process the question came up if we should also move the WebDriver classic tests from geckodriver to Marionette. Main reasoning is that more of the failures are actually in Marionette and not geckodriver. When doing that we will also have to move quite a bit of open bugs as well. With such a change we will then have both Mn and most of the wdspec tests covered by Testing / Marionette - or if we want to handle the JS side differently we could create a Remote Protocol / Marionette bug and leave Testing / Marionette for the client and harness.
|
||
Comment 5•2 years ago
|
||
| bugherder | ||
|
|
Assignee | |
Comment 6•2 years ago
|
||
We will move to Testing / Marionette. I'll file a bug for that.
|
|
Assignee | |
Updated•2 years ago
|
Description
•