W3C home > Mailing lists > Public > public-html@w3.org > January to March 2007

Re: story telling and test cases

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Tue, 27 Mar 2007 23:34:04 +1000
Message-ID: <46091D4C.7000706@lachy.id.au>
To: Dan Connolly <connolly@w3.org>
CC: public-html@w3.org

Dan Connolly wrote:
> I think I chose poorly when I picked the subject
> "brainstorming: test cases, issues, goals, etc."
> 
> What I really want is test cases; i.e. concrete documents
> sent as attachments.

Test cases for what?  Test cases don't really help when there's no 
structure.  Sure, we could all submit random test cases testing random 
features, but that doesn't really help anyone.

Good test cases should test a specific feature and have clear pass/fail 
conditions.  For mroe information about writing test cases, see the CSS 
2.1 test case authoring guidlines [1].  There's some good information in 
there, just ignore the CSS specific stuff.

The example "test cases" you mentioned can't really be considered test 
cases.  They're just demonstrations of features because neither 
expressed any pass/fail conditions.

So the question is, precisely what do you want test cases for?  What's 
your ultimate goal of having them?  What will make them useful for you 
specifically in this case?

[1] http://www.w3.org/Style/CSS/Test/guidelines.html#key-aspects

-- 
Lachlan Hunt
http://lachy.id.au/
Received on Tuesday, 27 March 2007 13:34:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2007 13:34:21 GMT