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

Re: Linking test suites to specs

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 24 Jun 2013 17:06:57 -0700
Message-ID: <CAAWBYDDbdEXHcVkacxwfActFmYHscPMyVD1+mSJomkyVbJS7Tg@mail.gmail.com>
To: Rebecca Hauck <rhauck@adobe.com>
Cc: www-style list <www-style@w3.org>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
On Mon, Jun 24, 2013 at 4:30 PM, Rebecca Hauck <rhauck@adobe.com> wrote:
> Hi all,
> Some of the CSS specs have a "Test Suite" in the header, which I presume was
> part of an original spec template. However, in the specs I've come across
> that have it, it's either not used/updated [1][2][3], or it's used
> inconsistently [4][5][6].
> I was talking to fantasai about this a while ago (in the context of defining
> Test Owners at the spec level) and she suggested we link to the test suite
> cover page that is part of the nightly build. For example, [7].
> In an effort to make this consistent across all the the CSS specs and for
> the clearest test suite visibility (even so we can clearly see when there
> are none), I'm proposing the following:
> Add the Test Suite section to all of the specs – those with no tests labeled
> "none yet"
> Link to the test suite cover page per fantasai's suggestion
> If this is put into place, I'll then be modifying & using the test suite
> cover page to include things like test owner(s), coverage data, tests
> needed, etc.
> Any objections?

Works for me.

Received on Tuesday, 25 June 2013 00:07:47 UTC

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