Prior-art action item

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

A remix of prior-art, based on Tim's input and what we already had in
prior drafts + wiki.

Suggest to split prior art in two:

(1) methodology complements about TAs. 
(2) examples of Tas.

At the end, some prior-art refs that I think do not qualify.

-Jacques


==================== Methodology about Tas: ===========================


-------------------------------------------------
W3C work on testing methodology:

   Work in W3C lead to the QA Framework: the Specification Guidelines
(W3C, November 2004) provides a more general overview of all
specification quality and conformance aspects, including the role of
test assertions.  
   http://www.w3.org/TR/qaframe-spec/  

   A cuccinct Test Assertion Guide was later drafted in W3C (W3C
Editors' Draft, 2006) 
   http://www.w3.org/2006/03/test-assertion-guide  

Another general FAQ about testing from W3C, showing the role of test
assertions:
http://www.w3.org/QA/WG/2005/01/test-faq
  
-------------------------------------------------
Unisoft Glossary:

Unisoft have published their own Glossary about testing, that includes a
definition and succinct categorization of Assertion. Intended for POSIX
standard.
http://www.unisoft.com/glossary.html 
[See also DejaGnu Testing Framework below.]

Gives a definition of test assertions relative to API and lists
different kinds of test assertions:
http://www.unisoft.com/test_assertions.html


-------------------------------------------------
The Voting Systems Standard (EAC), (2007):

http://www.eac.gov/files/vvsg/Final-TGDC-VVSG-08312007.pdf 
Shows the use of a categorization (classes and sub-classes) of test
assertion Targets. The object-oriented classification is used to
determine which requirements (and assertions) apply, e.g. by automatic
inheritance.  


-------------------------------------------------

http://karldmoore.blogspot.com/2007/11/unit-test-assertions-they-shouldn
t-be.html

This blog reports on common practical issues with assertion selection,
configuration, and messages for unit testing.  Some code examples are
given.

------------------------------------------------
 Google Test Primer (contains section on assertions): 

http://code.google.com/p/googletest/wiki/GoogleTestPrimer

A methodology guide from Google focused on a software development
environment. Develops a scripting approach to test assertions. Test
assertions are encoded as macros that resemble function calls. One tests
a class or function by making such assertions about its behavior.  


==================== Examples of Tas: ===========================

------------------------------------------------
Test Assertions from WS-Interoperability

http://www.ws-i.org/Testing/Tools/2005/01/BP11_TAD_1-1.htm

This document shows a systematic design of Test Assertions as a basis
for test suites that verify conformance to Web Service profiles. As test
assertions are better understood by end-users (as opposed to test cases
that are derived from them), WS-I test reports directly point at test
assertions to indicate reasons for failure or success.

------------------------------------------------
Test Assertions from HTML 4.01

http://www.w3.org/MarkUp/Test/HTML401/current/assertions/assertions_toc.
html 

A well-rounded set of test assertions for all aspects of the HTML
specification.

------------------------------------------------
Generic Assertions for Manual Testing, RC3: 

http://accessibility.freestandards.org/a11yspecs/kbd/kafs-gta-rc3.html

Describes minimal set of test assertions that must be developed to run
on an implementation of the Keyboard Access Functional Specification -
from Open A11y of Linux Foundation.  Assertions are described with
identifiers, titles, steps to take, and expected results.

------------------------------------------------
SOAP Version 1.2 Specification Assertions and Test Collection (2003)
http://www.w3.org/TR/soap12-testcollection/   

-------------------------------------------------
The DejaGnu Testing Framework - A POSIX conforming test framework - is
based on a use of test assertions
http://www.delorie.com/gnu/docs/dejagnu/dejagnu_6.html   
This builds on the POSIX assertions definitions and of particular note
is the analysis of outcome interpretations. The present guidelines do
not give extensive coverage to this because it is considered as more
relevant to test suites where outcomes can be related to the knowledge
of testing methods to be used.  

-------------------------------------------------
 Test Assertions at OpenSolaris.Org:

http://opensolaris.org/os/project/zfs-crypto/phase1/testassert/

Lists outlines of several assertions related to Open Solaris.   Format
of each
assertion is as follows: "_stc_assertion_start, ID, DESCRIPTION,
STRATEGY (with numbered steps), and "_stc_assertion_end".

http://www.genunix2.org/wiki/index.php/SCM_Test_Assertions
This page contains the test assertions for the OpenSolaris SCM Migration
Project in wiki format.  A number of assertions are listed, with edit
capability (permission needed).




================ Not sure we need to include these:


-------------------- may not use Test Assertion in the same sense we do:

http://xunitpatterns.com/Unfinished%20Test%20Assertion.html

Discusses some practical aspects in using test assertions: here to
handle incomplete test suites.   Incomplete tests fail by generating an
assertion that is guaranteed to fail..  
Some function/code examples are given.

 ------------------ not related directly enough to Tas?

Other methodologies for the creation of test assertions or similar
artefacts:

Constraint Languages have special relevance when defining test
assertions for specifications involving specification normative
statements which make use of standards such as XML Schemas and UML
diagrams.
Object Constraint Language (OCL) and Unified Modeling Language (UML),
Object Management Group, Inc. 
http://www.omg.org/technology/documents/modeling_spec_catalog.htm#OCL
OCL is a formal constraint language used to define constraints for UML.
It can have a special role in testing based on UML methodologies. It
includes methods for defining preconditions and prerequisites as well as
postconditions: There may be some overlap with test assertion
prerequisites. Where a specification includes UML diagrams it may be
useful to use OCL expressions within or in the place of test assertion
predicates. Similarly XPath expressions may play a key role in
predicates involving XML. In both of these special cases there may be
good reason to specialize the structure of the test assertion to
facilitate use of such expression languages. 
 
------------------- is more about conf clauses, does not talk of Tas:
(from our wiki)

Guidelines on Abstract Test Suites and Conformance Clauses - Norwegian
Technology Standards Institution