W3C home > Mailing lists > Public > www-qa-wg@w3.org > July 2004

[SpecGL Draft] E. Good Practice: Write Test Assertions

From: Karl Dubost <karl@w3.org>
Date: Thu, 15 Jul 2004 18:17:53 -0400
Message-Id: <D0EF62F0-D6AC-11D8-BAB6-000A95718F82@w3.org>
To: www-qa-wg@w3.org

Good Practice:
	Write Test Assertions

What does that mean?
	A test assertion is a statement of behavior, action, or condition that 
can be measured or tested. It is derived from the specification's 
requirements and provides a normative foundation from which or more 
test cases can be built.

Why should I care?
	Test assertions facilitate the development of consistent, complete 
specifications and promote the early development of test cases. This 
exercise helps to uncover inconsistencies, ambiguities, gaps, and 
non-testable statements in the specification. It can provide early 
feedback to the editors regarding areas that need attention. An added 
benefit is that the assertions can be used as input to test development 
efforts.

Related:
	TestGL?

Techniques:
	1. Do not input the feature inside a specification before to have 
associated test assertions.
	2. Create a template to write feature for the specification which 
includes test assertions.
	3. Identify all requirements in your specification and try to write 
corresponding test assertions.

Examples:
	When trying to write test assertions for all its conformance 
requirements, one Working Group found that informative information was 
needed to complete the normative requirement. Consequently, the 
conformance requirements were rewritten.

Examples given at
	http://www.w3.org/TR/2004/WD-qaframe-spec-20040602/#test-assertion-ex

-- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***

Received on Thursday, 15 July 2004 18:18:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:33 UTC