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

Re: Requirements for (level >=3) tests

From: Chris Lilley <chris@w3.org>
Date: Thu, 16 Feb 2012 21:05:28 +0100
Message-ID: <1875125880.20120216210528@w3.org>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: Øyvind Stenhaug <oyvinds@opera.com>, CSS-testsuite <public-css-testsuite@w3.org>
On Thursday, February 16, 2012, 7:57:17 PM, Boris wrote:

BZ> On 2/16/12 1:52 PM, Chris Lilley wrote:
>> I think we should also allow HTML5 (in the XML serialisation, so existing toolchain can consume it).

BZ> Does the existing toolchain consume reftest references?

No. But I didn't get the impression that Øyvind was talking about references only.

>> ØS>  Are #help<link>s always necessary for building?

>> If these are omitted them my understanding is that testing by chapter and reporting by chapter won't work.

BZ> Is this true specifically for reftest references, which is what Aryeh 
BZ> was asking about?

I wasn't responding to Areyeh in that part.

>> Similarly, without the assert of what is being tested, it is hard to check the tests, and its hard to auto-annotate the spec to link to the relevant tests.

BZ> It makes sense to put that information in the test.  I see no reason to
BZ> put it in the reference.

In my later response to Aryeh, I had missed that he was referring to reftest references only.




-- 
 Chris Lilley   Technical Director, Interaction Domain                 
 W3C Graphics Activity Lead, Fonts Activity Lead
 Co-Chair, W3C Hypertext CG
 Member, CSS, WebFonts, SVG Working Groups
Received on Thursday, 16 February 2012 20:05:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 February 2012 20:05:34 GMT