WSDL 2.0 Implementors,
I updated the WSDL 2.0 test suite to indicate indicate the violated assertion for bad documents. This info is in both the documentation element of the WSDL and the TestMetadata.xml file, e.g.
<?xml version="1.0"?>
<TestMetadata xmlns="http://www.w3.org/2006/02/wsdl/TestMetadata">
<Identifier>
http://dev.w3.org/cvsweb/2002/ws/desc/test-suite/documents/bad/Import-1B
</Identifier>
<Title>Bad Document Import-1B</Title>
<Purpose></Purpose>
<Description></Description>
<Status>accepted</Status>
<SpecRef></SpecRef>
<Preconditions>none</Preconditions>
<Inputs>XSDImport.wsdl</Inputs>
<ExpectedResults>
<Successful>false</Successful>
<ViolatesAssertion>Schema-0016</ViolatesAssertion>
</ExpectedResults>
<Version>1.0</Version>
<Contributor>
<Name>Lawrence Mandel</Name>
<Affiliation>IBM</Affiliation>
<EMail>[EMAIL PROTECTED]</EMail>
</Contributor>
<Rights>http://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231</Rights>
<Grouping>/documents/bad</Grouping>
<SeeAlso><Reference>http://www.w3.org/TR/wsdl20#Schema-0016</Reference></SeeAlso>
</TestMetadata>
I plan to update the Woden Ant task to write out a report of the failed assertions and then compare it to the expected assertions.
Note that good test cases might also violate non-mandatory assertions. Those would correspond to warnings, not errors. We need some of these added to the test suite.
I also plan to generate a coverage report so we can see how many test cases exists for each assertion in the spec. We clearly need to write a lot more test cases.
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: [EMAIL PROTECTED]
