Open Bug 1836785 Opened 1 year ago Updated 2 months ago

[wdspec] Implement infrastructure for running BiDi-only tests

Categories

(Remote Protocol :: WebDriver BiDi, task, P2)

Default
task

Tracking

(Not tracked)

People

(Reporter: Sasha, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Whiteboard: [webdriver:backlog])

At the moment, all wpt tests run with classic session and upgrade to bidi when it's required. But in certain case, we would like to test bidi session creation or run tests with bidi-only session. Most likely, each browser will need to create its own implementation, and we should get at the end something like fixture which would abstract it.
The drivers (geckodriver, chromedriver,...) could be used for it.

Blocks: 1833636
Blocks: 1838267
Depends on: 1839183
Component: web-platform-tests → WebDriver BiDi
Product: Testing → Remote Protocol
Summary: Implement infrastructure for wpt tests with bidi session only → [wdspec] Implement infrastructure for running BiDi-only tests

Hi Alex an Maksim. For now we filed this for tracking purposes on Bugzilla but a real PR should definitely be done upstream. Not sure right now if a RFC change would need to be requested.

What we would like to know for now is if you have already some Chrome-specific tests that use chromedriver to start a BiDi-only session to run some wdspec tests? If yes maybe you could point out some location that we potentially could use to improve the wptrunner and our wdspec fixtures to start BiDi-only sessions? We already have such infrastructure but it is only available in our repository for now.

Flags: needinfo?(sadym)
Flags: needinfo?(alexrudenko)
Priority: -- → P2
Whiteboard: [webdriver:backlog]

AFAIK chromium-bidi e2e tests run in BiDi-only mode https://github.com/GoogleChromeLabs/chromium-bidi/tree/main/tests
For WPT, Maksim is adding WebDriver BiDi support in https://github.com/web-platform-tests/wpt/pull/45823 (still in addition to the classic session)

Flags: needinfo?(alexrudenko)

(In reply to alexrudenko from comment #2)

AFAIK chromium-bidi e2e tests run in BiDi-only mode https://github.com/GoogleChromeLabs/chromium-bidi/tree/main/tests

I can still see the usage of the webSocketURL capability here:
https://github.com/GoogleChromeLabs/chromium-bidi/blob/main/tests/conftest.py#L106-L156

So it's still started via WebDriver classic and then the WebSocket connection is created. Or do I miss something?

For WPT, Maksim is adding WebDriver BiDi support in https://github.com/web-platform-tests/wpt/pull/45823 (still in addition to the classic session)

Yes, but that is for the testrunner, which is not used by wdspec tests.

Redirect a needinfo that is pending on an inactive user to the triage owner.
:whimboo, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE if it is not actionable?

For more information, please visit BugBot documentation.

Flags: needinfo?(sadym) → needinfo?(hskupin)
Flags: needinfo?(hskupin)
You need to log in before you can comment on or make changes to this bug.