W3C home > Mailing lists > Public > www-style@w3.org > October 2016

Re: PROPOSED RESOLUTION: merge csswg-test into web-platform-tests

From: Geoffrey Sneddon <me@gsnedders.com>
Date: Wed, 5 Oct 2016 16:06:28 +0100
Message-ID: <CAHKdfMg2PZ00wV7qdy8dM5oTkjGR8OqOW0Ry6x+KgDpbQzN99Q@mail.gmail.com>
To: Koji Ishii <kojiishi@gmail.com>
Cc: GĂ©rard Talbot <css21testsuite@gtalbot.org>, Public www-style mailing list <www-style@w3.org>
On Mon, Oct 3, 2016 at 6:38 PM, Koji Ishii <kojiishi@gmail.com> wrote:
> I agree with you in general, but as we try to move Writing Modes to PR/REC,
> Gecko and Blink have 100% test coverages for this test suite, we keep them
> up-to-date whenever tests were added/updated, and I need this view[1] to
> track our progress and status. Flexbox[2] has quite good test coverage too.
> What is rough time frame in your mind to make csswg-test read-only, and to
> have the better replacement for the test results? If the replacement of the
> results view comes earlier than read-only, or if the read-only is after
> Writing Modes REC, I'm fine.
> [1]
> http://test.csswg.org/harness/results/css-writing-modes-3_dev/grouped/filter/17/
> [2] http://test.csswg.org/harness/results/css-flexbox-1_dev/grouped/

Oh, maybe I should be clearer: the test harness will not stop working
because of making csswg-test read-only. It'll stop working when we
drop the build step, which will remain working within the css
subdirectory of web-platform-tests, and that'll happen once we have a

Received on Wednesday, 5 October 2016 15:06:59 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:15:01 UTC