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

Re: Requirements for (level >=3) tests

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 21 Feb 2012 20:40:56 -0500
Message-ID: <4F4447A8.7000302@mit.edu>
To: public-css-testsuite@w3.org
On 2/21/12 7:42 PM, Bjoern Hoehrmann wrote:
> 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

If the test is not easy to analyze, it's generally hard to impossible to 
tell whether the test is demonstrating a bug in the test or a bug in 
browsers, especially if several browsers agree on their rendering of the 
test.

Note that being easy to analyze is the important thing; good coding 
practice is only relevant insofar as it aids analysis.

-Boris
Received on Wednesday, 22 February 2012 01:41:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 22 February 2012 01:41:32 GMT