-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(webdriverio): manage browser drivers #10767
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some feedback, love seeing this 👍
de55212
to
5803144
Compare
a278825
to
1be58ae
Compare
fa8df51
to
e146c76
Compare
@christian-bromann Since you are working on this. Using selenium-standalone, From what I gather there is no API to do this. Maybe on CDP. AFAIK there is no way to do that at the moment. |
Can you explain what you mean by that. Please create a new issue for this because it is not necessarily within the scope of this PR. |
e146c76
to
6498ab5
Compare
8d1ed8d
to
18c1096
Compare
🎉 |
hi, when does this get released? |
It is, see release notes. |
ah thanks, sorry i was only looking at the 18.4.2 notes |
|
Proposed changes
This patch will change the current behavior that would default the execution to use
devtools
as automation engine and instead will setup and run a browser driver. Ultimately we want to deprecatedevtools
as WebDriver will provide everything needed. The maintenance of the package is not manageable and given all the new features in Bidi there doesn't seem much value to have WebdriverIO users run tests through Puppeteer.Types of changes
Checklist
Further comments
Missing items:
Reviewers: @webdriverio/project-committers