- From: Simon Fraser <smfr@me.com>
- Date: Wed, 29 Sep 2010 16:09:29 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: www-style@w3.org
On Sep 29, 2010, at 3:32 PM, Tab Atkins Jr. wrote: > On Wed, Sep 29, 2010 at 3:25 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> On Wed, Sep 29, 2010 at 1:15 PM, Simon Fraser <smfr@me.com> wrote: >>> I've been working on a test suite harness for the 2.1 test suite, in order to make running the tests faster. >>> >>> This harness is local-only, but uses a client-side (Web SQL) database to store results, so you can come back to the harness later and not lose results. Note that it assumes the tests are local, so cannot be used to run the tests that require http. >>> >>> The suite is in WebKit SVN here: >>> <http://trac.webkit.org/browser/trunk/WebKitTools/CSSTestSuiteHarness> >>> >>> Here are instructions for getting the WebKit code: >>> <http://webkit.org/building/checkout.html> >>> >>> You should just be able to checkout the WebKitTools/CSSTestSuiteHarness directory. >>> >>> The harness is work-in-progress, and has only been tested in Safari. Fixes/comments/suggestions welcome. >> >> Ooh, that's *excellent*. Thanks very much, Simon. Luckily I didn't >> do very many tests on the web version yesterday, because I can run >> through things ridiculously faster with this. > > Also, if anyone else is trying to use this, in order to get it to work > you have to follow these steps: > > 1. Run a local server. I'll assume that you create a folder called > CSSharness, and put the /harness folder from the webkit SVN in there. You can just run it from disk using file:// urls. > 2. Download all the tests. Put them in CSSharness/20100917/html4 (or > xhtml, as appropriate). > > 3. Put testinfo.data in CSSharness/20100917. Actually, just download the zip file (currently <http://test.csswg.org/suites/css2.1/20100917.zip>), extract it, and put the 20100917 directory next to the harness directory. > > 4. Run /CSSharness/harness/harness.html. Right. I should include some instructions. Main TODO items: * Throw up warnings for tests that need extra steps (i.e. those requiring a user CSS file, and paged media tests) * Allow importing of results from someone else so you can share work Simon
Received on Wednesday, 29 September 2010 23:10:04 UTC