[webkit-dev] Running layout tests for the chromium port, using the multi-processing architecture and fully sandboxed

[Jochen Eisinger]

Hey,

I've implemented initial support for running layout tests using chromium's
content_shell instead of test_shell as the current DRT implementation does.
It's still a very experimental, but might already be interesting for some
of you to try.

The main advantage is that content_shell includes chromium's full storage
implementation, so layout tests for indexed db are running against the
multi-processed IDB implementation instead of the simple stub used for DRT.

Here's how to build webkit with content_shell:

1. Make sure your WebKit is at least at r119852 (see
http://trac.webkit.org/wiki/Chromium for prerequisites)
2. Apply the attachment from https://bugs.webkit.org/show_bug.cgi?id=87045
3. In Source/WebKit/chromium run gclient sync
4. build webkit as usual

E.g. for a debug build on Linux, this should give you
out/Debug/content_shell

You can now run layout tests like this:

new-run-webkit-tests --chromium --debug --driver-name=content_shell
--additional-drt-flag=--dump-render-tree LayoutTests/storage/indexeddb/*

You'll notice that not all tests are passing yet, mainly because not all
(or actually, almost none of the) layoutTestController features are
implemented yet.

Another missing feature is producing pixel results. However, I'm currently
concentrating on text results, as I think the biggest benefit is the
ability to run storage tests on the real storage implementation.

Let me know if you have any feedback, comments, or questions. If somebody
is implemented in helping adding features (e.g. to get your favorite part
of the layout tests passing), I'm happy to point you at the code locations!

best
-jochen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120608/c353d4ff/attachment.html>