Hi Jeremy,
Currently the Woden test suite hard codes the W3C tests. We need to update our test suite to automatically pull down the latest W3C test suite and use it to test Woden including testing that invalid documents are flagged by Woden with the correct assertions. I'll open a Jira for this if one isn't open already.
Lawrence
| "Jeremy Hughes"
<[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 08/01/2006 07:14 AM
|
|
Hi, how about a coverage report for which of these WSDLs we test Woden against ?
Cheers,
Jeremy
On 8/1/06, John Kaputin <[EMAIL PROTECTED]> wrote:
>
> Key feedback from the recent WSDL 2.0 Interop event is that more WSDL 2.0
> test cases are needed to expand the coverage of the W3C test suite, so that
> the spec can move to Proposed Recommendation and Woden can move to a v0.9
> or v1.0 release. We (Woden) really need to help with this as there's not
> much contribution to the test suite from the WSDL 2.0 working group.
> Lawrence has already contributed a lot of test cases.
>
> There are now report pages on the WSDL 2.0 Working Group's site (
> http://www.w3.org/2002/ws/desc/) that indicate test case coverage for WSDL
> elements/attributes and for WSDL assertions. See the 'Test Coverage Report'
> and 'Test Assertion Report' links in the Test Suite section. From these we
> can work out what types of test cases are required. Creating test case WSDL
> documents is generally a case of copying an existing WSDL from the test
> suite and modifying it. There's a fairly lightweight process for
> contributing test cases as patches to the ws-desc mailing list which we can
> document on the Woden wiki, if it's not already documented by the WSDL
> working group.
>
> Perhaps we can discuss this further under A.O.B. on today's Woden call.
>
> regards,
> John Kaputin
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
