- From: Tobie Langel <tobie@w3.org>
- Date: Mon, 12 Aug 2013 08:55:08 +0200
- To: Simon Sapin <simon.sapin@exyr.org>
- Cc: "public-css-testsuite@w3.org mailing list" <public-css-testsuite@w3.org>
On Saturday, August 10, 2013 at 10:58 AM, Simon Sapin wrote: > Hi, > > A few months ago I wrote[1] about JSON-based CSS tokenization tests. The > conclusion is that they are not useful for W3C because tokens are (at > the moment) an implementation detail not exposed to the platform. > > These tests are now in a dedicated repository[2]. But more importantly, > I add tests for parsing <color> from CSS Color Level 3, and <An+B>[3] > from CSS Syntax Level 3 (ED). The latter is equivalent to what Selectors > Level 3 defines for :nth-child() and related selectors, except for > escaping in some cases[5]. > > These can be mechanically converted into reftests, testharness.js or > some other form of automated testing, which IMO is much more useful than > the current Color tests[5] that require visual inspection. This is awesome. What's your strategy for automating those? Also, messages that describe what the assertions are testing would be useful in some cases (when it's not obvious). --tobie
Received on Monday, 12 August 2013 06:55:15 UTC