W3C home > Mailing lists > Public > public-css-testsuite@w3.org > May 2008

RE: Testing SHOULD

From: Bonner, Matt (IPG) <matt.bonner@hp.com>
Date: Sat, 3 May 2008 00:58:34 +0000
To: fantasai <fantasai.lists@inkedblade.net>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-ID: <368F79A511563D43ADADF8B99EB82F1B40E99A42@G3W0637.americas.hpqcorp.net>

Thinking about how the SHOULD tests will help might offer
guidance for how to name them.

Obviously, these tests serve to see how UA's are doing; the
question that seems interesting to consider is what people
will conclude based on the results.

For example, if the results will guide decisions on which
SHOULD items should get promoted to MUST or dropped to MAY,
a flag name suggesting that idea seems helpful.

How do people expect testing SHOULD requirements to help?

Matt Bonner
Hewlett-Packard Company

-----Original Message-----
From: public-css-testsuite-request@w3.org [mailto:public-css-testsuite-request@w3.org] On Behalf Of fantasai
Sent: Friday, May 02, 2008 2:29 PM
To: public-css-testsuite@w3.org
Subject: Testing SHOULD

There are three levels of requirement in the CSS specs

MUST - the behavior is required
SHOULD/RECOMMENDED - the behavior is required unless there's a
                      good reason not to do it
MAY - the behavior is allowed

We're testing as many MUST requirements as we can, of course,
but it would be useful to also test SHOULD requirements. However,
we should distinguish these tests somehow from the MUST tests.
I was thinking to have a flag for SHOULD tests. Not sure what
to call it... optional? should? recommend?


Received on Saturday, 3 May 2008 01:00:16 UTC

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