W3C home > Mailing lists > Public > www-qa-wg@w3.org > April 2002

RE: New Definitons for Glossary

From: Kirill Gavrylyuk <kirillg@microsoft.com>
Date: Fri, 12 Apr 2002 19:12:39 -0700
Message-ID: <B3F0DACD72892E4DB7E8296C6C9FC2F605074EA8@red-msg-03.redmond.corp.microsoft.com>
To: "Karl Dubost" <karl@w3.org>, "Mark Skall" <mark.skall@nist.gov>, <www-qa-wg@w3.org>
"Invalid" or better "Error" test case is a test case that targets error
functionality of the product. Spec describes how the product
must/should/may handle the error cases, so the "Error" test cases target
testable assertions that describe error handling.  Still falls into the
definition Mark gave below.

Example:
Test for XML parser, provide non-wellformed xml as an input. This is an
"error" case that targets certain Wellformdness constraints.   

Good point that this is something common that should be probably added
to the Glossary.

Thanks

-----Original Message-----
From: Karl Dubost [mailto:karl@w3.org] 
Sent: Friday, April 12, 2002 5:17 PM
To: Mark Skall; www-qa-wg@w3.org
Subject: Re: New Definitons for Glossary


At 11:28 -0400 2002-04-12, Mark Skall wrote:
>Test Assertion
>A set of premises that are known to be true by definition in the spec. 
>Test Purpose An explanation of why the test was written, and must map
>directly to one or more test assertions.
>Test Case
>An individual test that corresponds to a test purpose,
>which in turn maps back to the assertion(s), and finally the spec.


I would like to know to people who are doing test cases something. It 
often occurs to me to create "invalid" test case. Their purpose is to 
test the behaviour of a client for example when the mark-up is wrong.

Is it still a test case? I'm a bit confused with the definition.


-- 
Karl Dubost / W3C - Conformance Manager
           http://www.w3.org/QA/

      --- Be Strict To Be Cool! ---
Received on Friday, 12 April 2002 22:13:14 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:09 GMT