W3C home > Mailing lists > Public > public-css-testsuite@w3.org > March 2012

Re: Submission of transform tests

From: Linss, Peter <peter.linss@hp.com>
Date: Fri, 23 Mar 2012 15:23:49 +0000
To: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <BD681138-9FC4-47F8-B46D-FACC47F2EF22@hp.com>

On Mar 22, 2012, at 3:48 PM, fantasai wrote:

> On 03/22/2012 11:18 AM, Aryeh Gregor wrote:
>> I decided to try porting some of my transform tests to the CSSWG
>> recommended format today, and move them to my submitted/ directory:
>> http://hg.csswg.org/test/rev/588481da9e8d
>> I got a whole bunch of errors:
>> ...
>> I imagine someone has to update Shepherd to tell it about the
>> transforms spec.  Is there anything else I need to fix?  The "Missing
>> <head>  element" error for an SVG seems like a mistake, but perhaps I'm
>> supposed to mark it somehow as a support file.  I don't want to port
>> any more tests until I'm sure I'm doing it right.
> Support files need to be inside a support/ folder.

Correct. The rules are:
Support files in a 'support' directory.
Reference files in a 'reference' directory (preferred), or have 'ref-' or 'notref-' filename prefix, or have '-ref' or '-notref' filename suffix (this will be expanded shortly to allow '-ref-' or '-notref-' within the filename).
Everything else is considered a test case.

Tests and references (in HTML or a known XML dialect) will be expected to have metadata in an HTML namespaced <head> element (this will be modified shortly for SVG to allow a different metadata container).

> I'm not sure how
> to import a new spec into Shepherd; Peter will have to take care of
> that.

I'll try to get to that today or the next few days

Note that we currently expect spec links in test cases to be to the version last published at http://www.w3.org/TR/, not drafts at dev.w3.org/csswg. So you'll have to update those links anyway (but wait until I update Shepherd).

There's been some discussion about allowing links to draft specs and having the build system adjust links on output, but there's nothing in place to support that yet, and the current general feeling is to disallow draft links to encourage more frequent publishing of drafts.

Received on Friday, 23 March 2012 15:25:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 20 January 2023 19:58:18 UTC