[webkit-dev] WebDriver support in WebKit

Ken Kania kkania at chromium.org
Tue Jul 24 09:36:39 PDT 2012

On Tue, Jul 24, 2012 at 7:12 AM, Žan Doberšek <zandobersek at gmail.com> wrote:

> On Mon, Jul 23, 2012 at 10:50 PM, Ken Kania <kkania at chromium.org> wrote:
>> The WebDriver w3c spec <http://www.w3.org/TR/2012/WD-webdriver-20120710/> was
>> recently published as a first public working draft.  The primary goal of
>> the API is to enable website testing from a user's perspective (finding
>> elements, typing, clicking).  Like the WebKit Inspector, WebDriver hopes to
>> aid developers in the process of developing/testing their website.
> Could it also be used in the layout tests? Looking through the spec there
> are APIs for mimicking mouse and keyboard interaction. This is pretty much
> what EventSender does, so could WebDriver replace the EventSender?

It is possible to expose some parts of the WebDriver API to JS just for
layout testing.  The WebDriver draft still has a TODO for the low level
input section<http://www.w3.org/TR/2012/WD-webdriver-20120710/#low-level-apis>,
but the current reference
a majority of the EventSender functionality.  Much of the lower level
gesture, touch, and scrolling methods are not included however.

>> Currently Chromium supports this API through a separately distributed
>> binary.  I wanted to get some feedback on the idea of supporting WebDriver
>> in WebCore itself (perhaps as a WebCore module, or perhaps in a similar way
>> as the WebKit Inspector).  The main benefit of this would be that the
>> WebDriver implementation could be shared among all interested WebKit ports.
> Continuing with the idea of WebDriver replacing the EventSender, I do
> wonder if it would be OK to bypass the native toolkit event handling and
> push the events straight into the WebCore's EventHandler.
> Also, the Capabilities and MutableCapabilities seem to do what is
> currently being done through either window.internals.settings or
> testRunner.overridePreference(), so this seems another thing for what the
> WebDriver implementation could be used instead of aforementioned object and
> method in layout tests.

It seems a bit of a stretch for WebDriver to be able to replace the
settings API.  WebDriver's Capabilities are pretty generic and are intended
to be used to query what parts of the WebDriver API are supported by the

>> Thanks
>> Ken
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo/webkit-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120724/ea18841d/attachment.html>

More information about the webkit-dev mailing list