The approach followed by SOAUnit is excellent. DSL should be nevertheless improved to allow to set which SOAP, WS-xxx (ws-security, ....) spec will be used and provide parameters according to the spec / headers
On Sun, Oct 6, 2013 at 11:49 PM, David MacDonald <dav...@cdonald.net.nz>wrote: > Hi guys, > > I've recently started work on SOAUnit > <http://uoa-group-applications.github.io/soaunit/> , a DSL for testing > external (or Camel internal) integration artifacts that uses Apache Camel > components and test framework. Basically our use case is to be able to > automatically 'unit' test mega-vendor enterprise service bus integration > artifacts where we don't have the same flexibility with testing that > something like Camel offers :). For example, if we have a PING web-service > running on the mega-vendor's ESB that simply returns PONG then we can use > the CXF component and Camel URI format: > > This will send the requestBody XML to localhost:8080, and check that the > XML > returned matches the expectedResponseBody. XML Comparisons are made using > XMLUnit to allow for textual representation variations. Furthermore, the > framework can support asynchronous transports and chaining of expectations > to ensure orchestrated processes function as expected. > > I'm interested in getting some feedback as to where it could be improved, > or > new features which could be useful. > > Thanks, > David > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Testing-DSL-based-on-Apache-Camel-tp5740992.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
