The WebDriver spec has been in development for a while and recently we have been getting new implementations. It would be great to see a webkit implementation for the following reasons: Simpler interop testing ======================= * Web-Platform-Tests, the test suite that implementors are contributing to, is starting to have WebDriver do some of the tests. Starting with just driving the browser to the correct state to in the future being able to do tests that are not bound by the JS sandbox like Testharness.js tests are * Web Developers and Testers can write one test script to run against all webdriver compliant browsers. This gives developers the confidence that their website works in all browsers and all platforms. Currently Implementations by W3C Members ======================================== ChromeDriver from Chromium. Works on Chrome for desktop and Android IEDriver from Microsoft. Currently on in their Developers release (http://status.modern.ie/webdriver) Marionette from Mozilla. Currently available for Firefox OS and Firefox Desktop OperaDriver from Opera. No longer available but was used for testing Presto BlackBerry WebDriver from Blackberry. Available for Blackberry 10+ http://devblog.blackberry.com/2014/02/selenium-support-in-blackberry-10/ Open Source Extensions of WebDriver =================================== Since Mobile is clearly the future we are seeing extensions of WebDriver to drive the Mobile OS. * Selendroid - Selenium for Android (Contributed to by eBay, Salesforce and Facebook and Adobe) - http://selendroid.io/ * IOS-Driver - Selenium for iOS (Contributed to by eBay, Salesforce and Google) - https://ios-driver.github.io/ios-driver/ This allows people to write a test once and be able to move them between all the different platforms and OSes. As a side note, Opera created their implemenation and fixed a number of bugs in it so that Google would test their products with Opera. Before that Opera was neglected as a users browser and created a number of issues for the browsers users. I would hate to see a potential monoculture to appear because people only test their sites with WebDriver supported browsers
<rdar://problem/13352830>
Brian, did you file another Web driver bug? Or are we still using this as an umbrella bug?
This is the bug we are using. There have been many subtasks that are not related to this bug, that we should relate at some point.
I have just seen this via the @webkit twitter account "in Safari 10, we are also bringing native WebDriver support to macOS." <https://twitter.com/webkit/status/743223358100111360> What this means for WebKit? Has this feature been implemented in another bug different than this one and I missed that? Is there any documentation about how it works or pointers about how other ports can enable this feature?
Some of the work has happened in WebKit, but the bulk of the WebDriver spec was implemented in Safari code due to integrations with Safari and using the macOS remote Inspector target discovery and protocol. The WebKit code is here: http://trac.webkit.org/browser/trunk/Source/WebKit2/UIProcess/Automation http://trac.webkit.org/browser/trunk/Source/WebKit2/WebProcess/Automation