W3C home > Mailing lists > Public > public-css-testsuite@w3.org > May 2012

Re: Build pre-CR "awaiting review" tests into the harness

From: Linss, Peter <peter.linss@hp.com>
Date: Tue, 15 May 2012 20:45:26 +0100
To: Alan Stearns <stearns@adobe.com>
CC: Public CSS test suite mailing list <public-css-testsuite@w3.org>
Message-ID: <DC304242-9B0D-4441-A6F6-4747CCA47BC0@hp.com>

On May 15, 2012, at 11:52 AM, Alan Stearns wrote:

(From the Hamburg minutes http://lists.w3.org/Archives/Public/www-style/2012May/0527.html )

   plinss: Suggest doing what we did with 2.1, build them into the test
           harness, run the tests, shift them into approved once the test
           suite seems stable, but don't give them reviewer links until
           they're individually reviewed


Is this something you'd be willing to do for pre-CR specs? I expect that no one really cares about reviews or the state of the test suite until the spec gets to that stage.

Yes, there are already existing builds to CSS Regions and CSS Transforms. As soon as there are enough tests they get included in the build.

Right now, someone (usually me) has to manually add the suite to the build. I have planned changes to the build system so it'll automatically build any test suite that has tests in a submitted or approved folder.

Note that it's still perfectly fine to approve tests  at any time via Shepherd and/or reviewer links. The discussion in Hamburg was to 'de-facto approve' any non-approved tests once we feel the test suite is stable enough (i.e., generally when we exit CR). Tests that get approved that way will not have reviewer links.

Received on Tuesday, 15 May 2012 19:46:49 UTC

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