[webkit-dev] Renaming directories
eric at webkit.org
Tue Dec 21 11:21:57 PST 2010
On Tue, Dec 21, 2010 at 1:14 PM, Darin Adler <darin at apple.com> wrote:
> Here’s my attempt to list the tests we currently have:
> - Manual regression tests (in WebCore/manual-tests directory). These would be in the primary regression tests if we found a way to automate them. A good project for a contributor would be to convert these to automated tests one at a time to try to empty this directory.
> - Automated DOM binding generation regression tests (in WebCore/bindings/scripts/test).
> - SVG page load test performance test (in PageLoadTests/svg). I am not familiar with this one.
I created this when I opensourced parts of Apple's PLT infrastructure
right before leaving Apple. It works, but no on uses it really. It
mostly serves as example data for run-pageloadtest.
> - Platform-specific unit tests (in WebKit/chromium/tests, WebKit/gtk/tests, and WebKit/qt/tests). Not familiar with these, how they are run, or what their coverage are.
> - Python regression tests. Not sure where they are, but I see these failing on the bots so I know they exist.
Any file which is under Tools/Scripts/webkitpy/ with the name
*_unittest.py will be assumed to contain python's unittest
module-style tests and will be automatically found and run by
Tools/Scripts/test-webkitpy. test-webkitpy also knows how to search
for python modules somewhere in WebKit2 (there are some used for some
code autogen) as well as python modules in Tools/QueueStatusServer
(soon to be Websites/queues.webkit.org?)
There are also perl unit tests in Tools/Scripts/webkitperl
There are also WebCore benchmarks in WebCore/benchmarks
There are bindings autogen tests in WebCore/bindings/test IIRC.
That's all I can think of.
> Maybe this list will give us some ideas about how we want to organize tests in the future.
> -- Darin
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev