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

Re: Proposal to refactor the CSS test repo

From: Tobie Langel <tobie.langel@gmail.com>
Date: Thu, 24 Apr 2014 00:36:31 +0200
Message-ID: <CAMK=o4f--daw4uPSNc3i9Ncwx_mxg36wW3miLre_aDk3OgxsWg@mail.gmail.com>
To: Rebecca Hauck <rhauck@adobe.com>
Cc: Peter Linss <peter.linss@hp.com>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
On Wed, Apr 23, 2014 at 6:57 PM, Rebecca Hauck <rhauck@adobe.com> wrote:

[...]

> I propose refactor the directories to use the spec short names just as the
> spec repo does.

This is a great move. Thanks for driving this.

[...]

> The proposed new structure:
>
> tests/[spec-shortname, spec-shortname…]
> test-plans/[spec-shortname, spec-shortname…]
> tools

May I suggest instead to adopt the same format already used in the WPT
repository, with shortnames at the root (eventually containing a test plan
within each directory).

> Also in full disclosure, I’m proposing this now as a precursor to another
> proposal I’d like to make to get the CSS repo more integrated (as a
submodule)
> of the WPT repo.  Since that is an entirely different different
discussion,
> I’ll reserve that for a different thread/list, but I think getting our
stuff
> well organized must come first.

Suggest you'd bring that up on public-test-infra@ asap.

All tooling built around WPT assumes specs are at the root of the
directory, using their shortnames. So including the CSS repo as a submodule
won't help you much here, unless you fix both open-source tools AND lobby
implementors to fix theirs (WPT is well on track to be part of most if not
all browser vendors CI environments in the near future).

Why not simply merge with the WPT repo? What technical issues prevent this?

Best,

--tobie
Received on Wednesday, 23 April 2014 22:37:00 UTC

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