Re: Linking test suites to specs

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 me making this proposed change to the spec header, I'll proceed (approximately this time tomorrow).

To reiterate, the changes I'll be making are:

 1.  Add the Test Suite section to all of the specs – those with no tests labeled "none yet"
 2.  Link to the test suite cover page per fantasai's suggestion

Thanks,
-Rebecca

From: Rebecca Hauck <rhauck@adobe.com<mailto:rhauck@adobe.com>>
Date: Monday, June 24, 2013 4:30 PM
To: www-style list <www-style@w3.org<mailto:www-style@w3.org>>, "public-css-testsuite@w3.org<mailto:public-css-testsuite@w3.org>" <public-css-testsuite@w3.org<mailto:public-css-testsuite@w3.org>>
Subject: Linking test suites to specs
Resent-From: <public-css-testsuite@w3.org<mailto:public-css-testsuite@w3.org>>
Resent-Date: Monday, June 24, 2013 4:36 PM

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:

 1.  Add the Test Suite section to all of the specs – those with no tests labeled "none yet"
 2.  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?

May I add this to the agenda for this week's meeting? Once I have consensus, I'll make the updates accordingly.

Thanks,
-Rebecca

[1] http://www.w3.org/TR/css3-transforms/ - "none yet"
[2] http://www.w3.org/TR/css3-transitions/ - "none yet"
[3] http://www.w3.org/TR/css-overflow-3/ - "none yet"
[4] http://www.w3.org/TR/css3-conditional/ - separate links to shepherd and the harness (suite interface)
[5] http://www.w3.org/TR/css-masking/ - links to the harness (runner)
[6] http://www.w3.org/TR/filter-effects/ - links to the harness (runner)
[7] http://test.csswg.org/suites/css3-transforms/nightly-unstable/