W3C home > Mailing lists > Public > public-css-testsuite@w3.org > March 2015

Re: testharness.js in CSS test repositry

From: Linss, Peter <peter.linss@hp.com>
Date: Sun, 29 Mar 2015 17:59:05 +0000
To: Koji Ishii <kojiishi@gmail.com>
CC: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <D72D5F4C-5E25-492A-BCB2-054753DB4FB1@hp.com>
On Mar 29, 2015, at 2:49 AM, Koji Ishii <kojiishi@gmail.com> wrote:

> I found 3 copies of testharness.js and testharnessreport.js:
> ./work-in-progress/ttwf_bj/Chris/testharness.js
> ./work-in-progress/ttwf_bj/Chris/testharnessreport.js
> ./work-in-progress/ttwf_shenzen/loutongbing/testharness.css
> ./work-in-progress/ttwf_shenzen/loutongbing/testharness.js
> ./work-in-progress/ttwf_shenzen/loutongbing/testharnessreport.js
> ./work-in-progress/ttwf_tokyo/resources/testharness.css
> ./work-in-progress/ttwf_tokyo/resources/testharness.js
> ./work-in-progress/ttwf_tokyo/resources/testharnessreport.js
> Could we have one? Should that be in “support” directory?

None of these should be in the repo at all. The testharness.js files are in their own repository at:

I have removed them.

The testharness.js repository should automatically be installed into your clone of the test repository in the 'resources' directory. (Mercurial users will see it the next time they pull and update, NOTE: you need to be using mercurial version 1.8 or later for this to work.)

If you're using a git clone of the css-test repository and the 'resources' directory is empty, then you need to init the submodules by running the following command in the root of your repository:
git submodule update --init --recursive


Received on Sunday, 29 March 2015 17:59:42 UTC

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