- From: Phil Adams <phil_adams@us.ibm.com>
- Date: Tue, 21 Apr 2009 16:11:15 -0500
- To: public-soap-jms@w3.org
- Message-ID: <OF01EAABC5.DC5FA150-ON8625759F.0073A585-8625759F.0074630F@us.ibm.com>
Hi everyone, I spent a few hours this afternoon updating the testcase documentation with the following changes: 1) I added two new testcases (test1009 and test1109) that deal with the new "unsupportedLookupVariant" fault subcode 2) I cleaned up some inconsistencies in some of the testcase entries (testcases.xml) 3) I went through the list of assertions and for some which were not currently "covered" by any testcase, I found testcases which do indeed cover those assertions so I updated the testcase entries to reflect that. The result is that the assertions table has fewer "uncovered" assertions. Most of the ones that are still uncovered probably can remain that way. For example, I don't think it would be useful to associate a testcase with Protocol-2024. Some of those "assertions" from the soap-jms binding spec aren't really test assertions at all as I discovered. Here's a link to the updated testcase docs: http://dev.w3.org/2008/ws/soapjms/testcases Thanks, Phil __________________________________________________________________________________________________________ Phil Adams (phil_adams@us.ibm.com) WebSphere Application Server Office: (512) 286-5041 (t/l 363) Web Services Development Cell: (512) 750-6599 IBM - Austin, TX
Received on Tuesday, 21 April 2009 21:12:05 UTC