W3C home > Mailing lists > Public > public-test-infra@w3.org > July to September 2017

Re: Unifying testsuite policy and getting rid of CSS exceptions

From: Philip Jägenstedt <foolip@google.com>
Date: Sat, 16 Sep 2017 03:51:40 +0000
Message-ID: <CAARdPYcmbirJTCtL2pRBWHw8w5HgH5JFMmtjNG8xfjZHQrE16A@mail.gmail.com>
To: Alan Stearns <stearns@adobe.com>, Geoffrey Sneddon <me@gsnedders.com>, public-test-infra <public-test-infra@w3.org>
On Thu, Sep 14, 2017 at 6:42 PM Alan Stearns <stearns@adobe.com> wrote:

> Given that there are costs associated with moving tests around, I’m
> slightly in favor of leaving current tests where they are.

Can you elaborate a bit on this? I don't disagree that there is *some*
cost, but at least from my vantage point it seems quite acceptable. When
tests are renamed we deal with it in the Chromium import process, and
doesn't require us to treat all of the renamed files as if they were new.
If there are other bits of tooling that don't handle renames well, I
wouldn't mind investing a bit of time fixing that.

I think that avoiding renaming makes the test suite more confusing over
time, e.g. html/ isn't organized per the current spec but how it once was.
What kinds of problems would we run into if we renamed some things in css/?
(Admission: I have already been doing exactly that in a few cases, and
nobody has told me to stop.)
Received on Saturday, 16 September 2017 03:52:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:13 UTC