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

Re: Towards a better testsuite: Build System

From: Ms2ger <ms2ger@gmail.com>
Date: Sat, 9 Apr 2016 20:38:02 +0200
Message-ID: <CAJ_uYVpmvA7B6kLAT5KRFxypMjPKUg9JSq21yq6RJeMKbtf0Mw@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: W3C CSS Mailing List <www-style@w3.org>, Mike Smith <public-css-testsuite@w3.org>
On Apr 9, 2016 4:32 PM, "fantasai" <fantasai.lists@inkedblade.net> wrote:
> On 04/09/2016 07:42 AM, Ms2ger wrote:
>> On Apr 8, 2016 19:01, "fantasai" <fantasai.lists@inkedblade.net <mailto:
fantasai.lists@inkedblade.net>> wrote:
>>> However, individual vendors may need scripts to convert the
>>> test-reference linkages into their preferred format E.g.
>>> for Mozilla, we do need to generate reftest manifest files,
>>> which are currently constructed by the build system. But
>>> that can be done with a lighter-weight system that just
>>> generates manifests in place per directory.
>> We don't, actually. We already run reftests from wpt using
>> its manifest format; there's no reason to use reftest.list.
> Right, but the CSSWG tests don't have any manifest; we use
> <link> tags intead. So we'd need to generate some kind of
> manifest, whether it's in WPT format or reftest.list format.

So does wpt; we went out of our way to use the exact same semantics for the
link elements in wpt and csswg-test.

Received on Saturday, 9 April 2016 18:38:35 UTC

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