W3C home > Mailing lists > Public > www-archive@w3.org > February 2017

Building CSS test suites from web-platform-tests

From: Geoffrey Sneddon <me@gsnedders.com>
Date: Fri, 24 Feb 2017 17:59:49 +0000
Message-ID: <CAHKdfMhBK9GmBBc99-96oLyFLvPx7nFEdPgAyyYhMHsf6NLUrw@mail.gmail.com>
To: Peter Linss <peter@linss.com>
Cc: www-archive <www-archive@w3.org>
Hi,

I think we're close to being ready to merge the two test suites now.

The one item on the to-do list that's out of my control is making sure
the test harness still gets the test suites; as agreed before the CSS
build system is just remaining pretty much as-is in the short term,
hence it's mostly making sure the test harness pulls from git and
builds from there.

https://github.com/w3c/web-platform-tests/tree/csswg_test_merged has a
merged tree (note, however, that I am intermittently force-pushing to
that branch; the merge commit will always be the top of it).

Notably, the css subdirectory is essentially just csswg-test, though
note that w3ctestlib and apiclient are now git submodules of the repo.
There's now a css/build-css-testsuites.sh which should probably be the
recommended way to build the testsuite given it deals with
requirements. Of course, you can always just cd css; python
tools/build.py and then look in dist.

Obviously you don't want to actually make the web-platform-tests
script the active script until we've actually done the merge, but do
you have any idea of by when you could alter the script for it?

/gsnedders
Received on Friday, 24 February 2017 18:08:59 UTC

This archive was generated by hypermail 2.3.1 : Friday, 24 February 2017 18:09:00 UTC