W3C home > Mailing lists > Public > public-css-testsuite@w3.org > April 2014

Re: Proposal to refactor the CSS test repo

From: Peter Linss <peter.linss@hp.com>
Date: Thu, 24 Apr 2014 19:28:53 -0700
Cc: Rebecca Hauck <rhauck@adobe.com>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-Id: <2DAC5C15-3F6D-4ED3-8E5E-0A3BF4E3EB26@hp.com>
To: fantasai <fantasai.lists@inkedblade.net>

On Apr 24, 2014, at 4:10 PM, fantasai <fantasai.lists@inkedblade.net> wrote:

>> [stuff about test repo reorg and symlinks]
> 
> Let's *not* do symlinks. Just put the test in the most specific directory
> and leave it at that. That's the policy we currently have. If you're
> searching for all tests linked against a particular spec, you'll just have
> to use Shepherd or the build tools.

Works for me, if someone really needs the tests to be in each spec directory for a test harness, we can make a quick script to make those copies based on the spec links. But for CSS tests people should really be running the output of the build anyway.

> 
> If Peter thinks we don't need cvs-import or build-test, then we probably
> don't need it.

We definitely donít need and of the scripts in those directories, theyíre not being used anymore. If someone ever needs to refer to them, we have mercurial history.

Iím a bit more concerned about some of the test files in those directories, from a quick look they appear to be old tests that were in a state of being converted into the current format. I donít know if thatís been done and those are the old versions, or if there still are some tests there that should be converted that have been left behind...

> 
> Rebecca, before you do this, please check in with a rep from each vendor.
> There might be import/export setups on their end that would need to be
> adjusted. For Mozilla, you can ask dbaron, he would know.
> 
> ~fantasai
> 


Received on Friday, 25 April 2014 02:29:20 UTC

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