W3C home > Mailing lists > Public > public-css-testsuite@w3.org > June 2010

Re: CSS2.1 Test Suite Beta 1

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 16 Jun 2010 12:14:15 -0700
Message-ID: <4C192287.20403@inkedblade.net>
To: "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
On 06/16/2010 11:17 AM, Boris Zbarsky wrote:
> On 6/16/10 2:04 PM, fantasai wrote:
>> On 06/16/2010 10:41 AM, Boris Zbarsky wrote:
>>> On 6/16/10 4:22 AM, fantasai wrote:
>>>> I'm pushing the rest of the tests to the server. I can't fix all of
>>>> this tonight. And I still haven't gotten to any CSS2.1 issues. These
>>>> will have to wait for the next release.
>>> Hold on. Does "next release" mean "beta 2"? Or does "next release" mean
>>> something else?
>> Next release is either Alpha 4 or Beta 1 -- I just posted yesterday's
>> release as an Alpha.
> OK, great. Can I do something to help integrate those tests, then?

Um, sure. :) The two problems that prevent me from building the tests
at all are
   - support files not in a support subfolder
   - conflicting filenames across folders

dbaron is maintaining the tests as an auto-import from Mozilla's tree,
so the changes would have to be made there.

The other problems in the tests are that the filenames don't match the
CSS filename format (test-topic-###.xht) and many of them have overly
simplistic (and thus repetitive) titles. But these don't break the build
process. I have a partial patch for fixing the filenames of the
bug-numbered tests in my tree. The 234686 tests are already imported
into the tree as
We can create a single reference file for that, and Mozilla's copy
will no longer be necessary.

[switching CC to public-css-testsuite@w3.org]

Received on Wednesday, 16 June 2010 19:14:53 UTC

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