On Fri, Jul 13, 2012 at 1:10 PM, Jochen Eisinger <[email protected]>wrote:
> On Fri, Jul 13, 2012 at 7:46 PM, Ryosuke Niwa <[email protected]> wrote: > >> On Fri, Jul 13, 2012 at 4:16 AM, Jochen Eisinger <[email protected]>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 > content_shell. > > 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? Adam
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
