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 19:52:00 +0100
Message-ID: <1379075221.20120216195200@w3.org>
To: Øyvind Stenhaug <oyvinds@opera.com>
CC: CSS-testsuite <public-css-testsuite@w3.org>
On Thursday, February 16, 2012, 5:29:39 PM, Øyvind wrote:

ØS> I have assumed that the guidelines at  
ØS> http://wiki.csswg.org/test/css2.1/contribute etc also apply to non-CSS2.1
ØS> tests, even though the URLs, breadcrumbs and content tend to mention 2.1
ØS> specifically.

I agree that should be updated to clarify.

ØS>  Whether this is true or not, I am wondering which parts are
ØS> absolutely *required* for submitted tests. Maybe that could be stated more
ØS> clearly.

ØS> For instance, is the XHTML format mandatory for other testsuites? (It
ØS> seems not all of them use it.) 

I think we should also allow HTML5 (in the XML serialisation, so existing toolchain can consume it).

<!DOCTYPE html>
<html>
 <head>
  <title>CSS Test: DESCRIPTION OF TEST</title>
  <link rel="author" title="NAME_OF_AUTHOR" href="mailto:EMAIL OR http://CONTACT_PAGE"/>
  <link rel="help" href="RELEVANT_SPEC_SECTION"/>
  <meta name="flags" content="TOKENS" />
  <meta name="assert" content="TEST ASSERTION"/>
  <style type="text/css">
   CSS FOR TEST
  </style>
 </head>
 <body>
  CONTENT OF TEST
 </body>
</html>

Ø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.

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.

ØS> Of course, if I write a new testsuite I will try to keep all of these
ØS> guidelines in mind. However, for existing and more ad-hoc tests, and tests
ØS> written by others, the higher the bar the harder it will be to find the
ØS> required time to do all the work for converting and submitting.





-- 
 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 18:52:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 16 February 2012 18:52:13 GMT