Assertion Reviews, Test Suite Coverage, and TestMetadata.xml

After everyone completes their assigned review of the spec for assertions 
[1]. the next step is to add test cases to the test suite to cover the 
assertions. For document or component assertions, this means creating a 
schema valid WSDL document that violates the assertion.

I've created an XML format, TestMetatdata.xml,  to capture the information 
about each test case. It is based on [2]. For an example of one see [3]. 
I've created one for each test case. When you create a test case, please 
alway create a TestMetadata.xml to describe it (just copy and edit the 
Chameleon-1B example).

This metatdata will let us determine how well the assertions are covered. 
I'll generate a coverage report that compares the test suite to the spec. 
It will also let us check the correctness of Woden which returns the 
violated assertion id. 

[1] 
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/assert-yourself.html#review-assignments
[2] http://www.w3.org/TR/test-metadata/
[3] 
http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Chameleon-1B/TestMetadata.xml?rev=1.2&content-type=text/x-cvsweb-markup

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca