As mentioned in a previous thread, we now have enough infrastructure
in place to run WebKit's layout tests on Linux.  Here's a bit more
info about how to get involved.

If you build a test_shell executable the instructions on the
development site are a good place to start:
  http://dev.chromium.org/developers/testing/webkit-layout-tests

Here's what we want to do, in rough order of priority:
1) Be able to run all the tests without any of them hanging.  This is
especially important because it slows down the test runner.
2) Be able to run all the tests without any of them crashing.
3) Pass tests that don't rely on font metrics.
4) Pass tests that rely on font metrics.
5) Pass pixel tests.

Right now our tests compare against our Windows-based baseline
expected output, which means, due to font rendering differences, the
outputs don't match exactly.  Some talented people are looking into
whether we can match Windows metrics (e.g. "disable antialiasing"), so
don't worry yet about tests that have different positional output --
we still have plenty of tests that are oughtright failing due to
missing code.

If you start poking into something, it might help to mention it on IRC
so we can try to avoid duplicating effort.

Finally, we've collected some Linux-specific tips and tricks here:
  http://code.google.com/p/chromium/wiki/LayoutTestsLinux
In particular, you can run the tests within a nested X server which
means you can run them without them hijacking your computer, and in
theory we'll be able to run them in parallel in the future.  Please
edit that page (it's world-editable) with any other notes you may
have.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/chromium-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to