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

Test Assertions for Guideline 3 for SpecGL

From: Mark Skall <mark.skall@nist.gov>
Date: Thu, 19 Dec 2002 11:03:42 -0500
Message-Id: <5.1.0.14.2.20021219105010.01fdb570@mailserver.nist.gov>
To: www-qa-wg@w3.org
To all,

Below are a set of assertions I developed for each checkpoint in Guideline 
3 of SpecGL.  These are scheduled to be discussed in Seattle wrt to the 
issue of whether or not the "to fulfill" statement is sufficient enough to 
be considered a test assertion.

Please note that, although there are some similarities with the "to 
fulfill" statement, these test assertions are more specific and, in some 
cases, go down a level deeper in detail (e.g., checkpoint 3.3).

Also, in some cases, it was necessary to read the Rationale section to be 
able to figure out what we really wanted and write the test assertion.  All 
the info was not contained in the "to fulfill" statement.

Mark




Assertions for Guideline 3.  Specify Conformance Policy

Checkpoint 3.1. Specify any universal requirements for minimum 
functionality. [Priority1]
To fulfill this checkpoint, a specification MUST include a normative 
section detailing any universal requirements for minimum functionality. It 
is not applicable if there are not any universal requirements.


Assertion: The specification contains a section stating universal 
requirements for minimum functionality.  ELSE there are no requirements for 
minimum functionality AND ckpt 3.1 does not apply.

Checkpoint 3.2. Identify strict conformance requirements. [Priority1]
To fulfill this checkpoint, a specification MUST state in its conformance 
section if the conformance requirements are strict or identify the kinds of 
variability that are permitted

Assertion: The specification's conformance section contains strict 
conformance requirements OR the specification details the explicit kinds of 
variability permitted.

Checkpoint 3.3. Distinguish requirements from product-specific extra 
features [Priority1]
To full this checkpoint, a specification MUST state in its conformance 
section all facets of the requirements where the required features 
represent the maximum allowable capabilities.


Assertion: If strict conformance does not apply, THEN the specification's 
conformance section contains a section identifying the maximum allowable 
capabilities for applicable required features.  ELSE ckpt 3.3 does not apply



Checkpoint 3.4. If special conformance terms are used, include a definition 
in the specification. [Priority1]
To fulfill this checkpoint, a specification MUST either exclusively use 
conformance terms as defined in this document or define any other 
conformance terms used in it and reference them from the conformance clause.

Assertion: (The specification contains a definition of new conformance 
terms AND the specification's conformance clause references these terms) OR 
the specification DOES NOT use any conformance terms not defined in SpecGL.

****************************************************************
Mark Skall
Chief, Software Diagnostics and Conformance Testing Division
Information Technology Laboratory
National Institute of Standards and Technology (NIST)
100 Bureau Drive, Stop 8970
Gaithersburg, MD 20899-8970

Voice: 301-975-3262
Fax:   301-590-9174
Email: skall@nist.gov
**************************************************************** 
Received on Thursday, 19 December 2002 11:11:29 GMT

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