W3C home > Mailing lists > Public > public-css-testsuite@w3.org > February 2012

Re: Requirements for (level >=3) tests

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Wed, 22 Feb 2012 01:42:53 +0100
To: css21testsuite@gtalbot.org
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, "Public CSS testsuite mailing list" <public-css-testsuite@w3.org>
Message-ID: <g3e8k75gnsr56up7e66sdhip8vi5gn17mq@hive.bjoern.hoehrmann.de>
* Gérard Talbot wrote:
>The CSS2.1 test suite could have been created in a way that would test
>implementations *and* consider everyone else related to/concerned about
>CSS (web authors, book authors, tutorials, etc.) It's too late now to
>wish for that.
>
>If the CSS2.1 test suite is not using best coding practices when writing
>tests, then it should invite contributors to do so. Loud and clear.
>Intentionally. In the wiki about test format guidelines.

The problem the test suite is meant to solve is that sometimes authors
write certain style sheets and browser behave differently in manners
they could not reasonably be expected to anticipate or are otherwise
bad. In other words, they are meant to draw attention to problems that
need to be solved. If the tests are easy to analyze or follow what's
considered good coding practise, that's nice, but anything that goes
beyond "reveal implementation and specification problems efficiently"
draws resources away from the actual problem to be solved. Certainly if
you consider test suites with worse coverage than the CSS 2.1 suite, in
particular all those that do not exist at all.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Wednesday, 22 February 2012 00:43:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 22 February 2012 00:43:23 GMT