[webkit-dev] Updates on Chromium's content_shell
jochen at chromium.org
Fri Jul 13 13:56:43 PDT 2012
What about keeping the discussion here, so others that might want to join
the effort later can read it up?
In general, I agree with your proposal. I guess starting with something
small like EventSender might be a good first step.
On Fri, Jul 13, 2012 at 10:20 PM, Adam Barth <abarth at webkit.org> wrote:
> On Fri, Jul 13, 2012 at 1:10 PM, Jochen Eisinger <jochen at chromium.org>wrote:
>> On Fri, Jul 13, 2012 at 7:46 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
>>> On Fri, Jul 13, 2012 at 4:16 AM, Jochen Eisinger <jochen at chromium.org>wrote:
>>>> I wanted to share some updates about content_shell (a multi-processed
>>>> version of chromium's test shell): meanwhile, it is possible to generate
>>>> pixel results.
>>>> Out of 31431 tests that are executed on chromium-linux, 6234 did not
>>>> match the expected results using content_shell, all others passed (80.17%)!
>>> This is a great news! Thanks a lot for working on this effort. Let us
>>> know if you needed a help in implementing testRunner methods.
>> At this point, there are two things I could use help with: in general,
>> moving methods to window.internals (and addressing the current shortcomings
>> of that approach) helps a lot, as I can just instantiate this object in
>> The other thing is to work towards making layoutTestController (of
>> chromium's DRT) a library.
>> Adam mentioned a while ago that he'd be interested with helping with the
>> latter as well
> Yes. The idea is to implement LayoutTestController in terms of the WebKit
> API and a (hopefully simple) delegate. Currently LayoutTestController
> knows too much about DumpRenderTree. That will let us share the
> implementation of LayoutTestController and avoid having to maintain yet
> another copy.
> Upstreaming the chromium-android port is at the top of my priority list,
> but I should be able to help out with this work as well. Should we talk
> off-list about how to approach this work?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev