W3C home > Mailing lists > Public > www-archive@w3.org > March 2016

Re: Using wpt for CR exit

From: Geoffrey Sneddon <me@gsnedders.com>
Date: Tue, 29 Mar 2016 13:39:39 +0100
Message-ID: <CAHKdfMjCxtuUeJ2nvbm=5qchpR-vZ_0fPi6rz5T_0HczGqqctg@mail.gmail.com>
To: Philippe Le Hegaret <plh@w3.org>
Cc: www-archive <www-archive@w3.org>
On Tue, Mar 29, 2016 at 1:22 PM, Philippe Le Hegaret <plh@w3.org> wrote:
> On 03/29/2016 12:33 AM, Geoffrey Sneddon wrote:
>> As an aside: there's been some discussion in the CSS WG about testsuites
>> recently (uh, my doing, "whoops") which you might have some interest in,
>> some of which deals with issues like testsuites for different versions
>> of a spec.
> I'll try to catch up on this front. I'm curious about the use cases for the
> old test suites. While I can think of some, I'm worried about the added
> costs for maintaining multiple versions of a test suite. We already have
> such difficulties for maintaining multiple versions of a spec...

I think the most obvious thing that comes to mind is the long period
it took to get CSS 2.1 out of CR, and the deferment of a number of
features to level 3. This meant punting a number of tests to their
respective level 3 modules (display: run-in comes to mind as something
that affected a lot of tests), while simultaneously maintaining the
2.1 testsuite for the sake of getting it out of CR. On the other hand,
things like that are almost certainly doable with simple filtering of
tests given an increasingly large blacklist can be used.

Received on Tuesday, 29 March 2016 12:40:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:35:30 UTC