-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Switch WebKit browser product to WebDriver executors #13339
Switch WebKit browser product to WebDriver executors #13339
Conversation
Switch away from Selenium executors to WebDriverTestharnessExecutor and WebDriverRefTestExecutor for the WebKit browser product. For the moment this requires manually mapping Selenium-style capability names to the W3C equivalents that can be handled by WebKit's WebDriver implementation. The browserVersion value is also hard-coded to the 2.20 release series for the GTK+ port of WebKit as that's when the WebDriver functionality was introduced.
What testing have you done of this? Have you run at least |
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.
I like the idea here, but it would be good to remove the dependency on Selenium entirely.
@@ -43,6 +43,16 @@ def capabilities_for_port(server_config, **kwargs): | |||
"certificateFile": kwargs["host_cert_path"]} | |||
] | |||
} | |||
|
|||
# Manually map Selenium's key names to the corresponding W3C versions. |
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.
Couldn't you just statically define a set of capabilities rather than still depending on the selenium defaults? Looks like the DesiredCapabilites.WEBKITGTK capabilities are rather simple anyway.
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.
Yeah I'll do that.
A small set of tests is run currently. Nothing changes there. Things in
Now:
|
Switch away from Selenium executors to WebDriverTestharnessExecutor and
WebDriverRefTestExecutor for the WebKit browser product.
For the moment this requires manually mapping Selenium-style capability names
to the W3C equivalents that can be handled by WebKit's WebDriver implementation.
The browserVersion value is also hard-coded to the 2.20 release series for the
GTK+ port of WebKit as that's when the WebDriver functionality was introduced.