W3C home > Mailing lists > Public > public-css-testsuite@w3.org > June 2013

Re: Linking test suites to specs

From: Rebecca Hauck <rhauck@adobe.com>
Date: Thu, 27 Jun 2013 15:15:46 -0700
To: "Tab Atkins Jr." <jackalmage@gmail.com>
CC: www-style list <www-style@w3.org>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <CDF2040E.334EE%rhauck@adobe.com>

On 6/27/13 2:40 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote:

>On Thu, Jun 27, 2013 at 2:06 PM, Rebecca Hauck <rhauck@adobe.com> wrote:
>> This never made it on to the already full agenda of yesterday's meeting
>> I'm not even sure it requires that precious time.  If no one objects to
>> making this proposed change to the spec header, I'll proceed
>> this time tomorrow).
>> To reiterate, the changes I'll be making are:
>> Add the Test Suite section to all of the specs  those with no tests
>> "none yet"
>> Link to the test suite cover page per fantasai's suggestion
>What'll the markup look like?  Either a "none yet" string, or a link
>to the test suite cover page?  What text should the link contain -
>just the link itself, or something else?

Yes, either "none yet" or a link to the cover page. For example:


And just the link is fine.

However, these test suite links have versions in them - is that going to
be problematic? Input from Peter is welcome here as I'm not super familiar
(yet) with these things are built and labeled.

>(Asking so I can add to my preprocessor, since you can't directly edit
>the boilerplate on specs using it.)
Received on Thursday, 27 June 2013 22:16:04 UTC

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