W3C home > Mailing lists > Public > public-css-testsuite@w3.org > December 2011

Re: 28 proposals to improve testcase writing guidelines

From: Gérard Talbot <css21testsuite@gtalbot.org>
Date: Thu, 8 Dec 2011 16:44:00 -0800
Message-ID: <87748c1283b27b3fb0c48f4819978e27.squirrel@gtalbot.org>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: "Public CSS test suite mailing list" <public-css-testsuite@w3.org>

Le Mar 6 décembre 2011 14:22, L. David Baron a écrit :
> These seem like 28 proposals to improve test *cases*, but it's not
> clear to me how you intend them to affect the *guidelines*.
> I'd be very hesitant to add 28 rules like these to the guidelines,
> because it makes it much harder for people to get started writing
> testcases, and it makes it harder to convince people that writing
> testcases according to the guidelines is easy to do and worth doing.
> If they could be boiled down to a few sentences I'd be much happier
> adding to the guidelines.


If someone is going to submit 5 or 10 tests, then (s)he does not need to
read such 28 rules or to read anything. (S)he can just contact me.

If someone is going to submit 50 tests, then (s)he does not need to read
such 28 rules but (s)he should at least read
Test Format
(S)he can contact me while editing a few tests too or ask for advice in
this mailing list.

Finally, if an IT corporation or a dedicated test author (eg Ian
Hickson) intends to submit more than 100 testcases, then I think such IT
corporation or test author should read all relevant documents (including
the one on my 28 proposals) about creating good testcases. So far, only
3 entities fit such profile and have submitted over 500 tests in the CSS
2.1 test suite: Microsoft, Mozilla and Ian Hickson.

The more a person or organization submit tests, then the more, I feel,
it is important that such person or organization should try to make - as
much as humanly possible - impeccable and compliant tests. And in my
mind, there is a hierarchy of importance and relevance too when a test
does not comply with guidelines.

In general, most of my 28 proposals are already given in more general
terms in
Reviewing Tests: Review Checklist
and in
CSS Test Review Checklist

regards, Gérard
Contributions to the CSS 2.1 test suite:

CSS 2.1 Test suite RC6, March 23rd 2011:

CSS 2.1 test suite harness:

Contributing to to CSS 2.1 test suite:
Received on Friday, 9 December 2011 00:44:41 UTC

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