Graham,
The Ant task can capture the errors reported by the parser and write them to an XML report file. I am going to write an XSLT stylesheet that reads the report and compares it to the expected results as defined by the
TestMetadata.xml file. e.g. for Binding-1B the assertion should be Binding-0055 [1]. I will attempt to complete this before the event, but failing that, I'll do it there.
On 11/8/06, Lawrence Mandel <[EMAIL PROTECTED]> wrote:
Hi Graham,
You're correct that the current JUnit tests do not check for expected assertion failures. This needs to be updated and Arthur volunteered to take on work as part of his update for the Ant task that he's already written.
The working group has made progress on their side to assist with this testing. Every WSDL test case now contains a metadata file that lists the expected assertion failures, which Woden should be able to use to test the validation component.
Lawrence
Graham Turrell <[EMAIL PROTECTED]> 11/08/2006 07:25 PM
[email protected]
[email protected] W3C Test Suite ant tasks
Hi Arthur (and Lawrence),
Looking at the JUnit version of the W3CTestSuite snapshot in Woden, I
notice that the "bad" (negative) tests do not check that a
specific assertion has been violated. Each test simply verifies that a
non-null DescriptionElement is returned by the WSDLReader.
Does the current version of the test suite check for expected assertion
failures on the "bad" tests, and if not are there any plans to add this
yet?
(I see that WODEN-39 [1] exists as a placeholder to cover this in the Woden
test suite, but wondering what work might have been done on the working
group side)
Thanks.
Kind Regards,
Graham.
[1] http://issues.apache.org/jira/browse/WODEN-39
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
