Comments on: soapUI vs. JUnit

By: Sourabha

Sourabha — Tue, 02 Mar 2010 08:23:48 +0000

I have done schema validation for synchronous services using SOAP UI. i tried doing validation of asynchronous services but i could not figure it out properly. i would also like to know how we do load and stress testing using this tool.

By: Anand

Anand — Mon, 30 Nov 2009 07:22:33 +0000

Good Post..I got exactly what I want. This saved at least an hour for looking around.
I follow all your posting in SOA section as well..
Many Thanks

By: Krishna

Krishna — Tue, 04 Aug 2009 06:31:45 +0000

I am new to SOAPUI and want to know how to invoke API from SOAPUI
Can you please let me know, what steps need to be followed to invoke the API?

By: July

July — Thu, 04 Jun 2009 17:41:36 +0000

Hello,
I need your help…………. I am trying to connect a web service, but it doesn’t work using JAX-WS API, but when I test it with the soapUI tool it works, so I want to know how soapUI works……………it is very important, please is someone can help me?

Thanks in advance,
July

By: sure

sure — Thu, 17 Apr 2008 05:16:08 +0000

Hi,

I am new to this tool, Can any one help me how to test webservice using this tool,

By: Alexander Ananiev

Alexander Ananiev — Wed, 02 May 2007 14:28:01 +0000

Ole, I agree with you on #2 in that typically service consumers would be using different types of Web services platforms, not just JAX-WS (otherwise, what would be the point of using Web services in the first place). However, from my experience, in a corporate environment (Internet is a totally different matter) these technologies are limited to mostly different flavors of Java and .NET and so there are not that many permutations that would have to be tested using XUnit approach.

On #3, I actually think that generating JUnit stubs from soapUI would somewhat defeat the purpose of developing JUnit classes, which is to allow service providers to perform all the steps that service consumers would have to go through in order to consume a service. And I’m pretty sure that you already have enough on your plate with all the other work on soapUI :)

Thanks for the great tool,
Alexander

By: Ole Matzura

Ole Matzura — Tue, 01 May 2007 11:43:44 +0000

Hi,

nice post! I would like to add some more twists:

1) Using a tool like soapUI is mainly for testing the actual server-side web service implementation, and does give some possibilities that are not available (or at least not easy) in JAX-WS;
- sending of invalid messages (both syntactically and structurally) which is usefull for testing server-side error handling,
- sending of messages using standards not supported by JAX-WS (much of the WS-XXX soup)

2) Often when developing web services, you have little control of the actual client technology used on “the other side”, thus providing examples based on JUnit/JAX-WS could be rather limited as there are so many more technologies in use for accessing web services (but of course its better than no examples at all).
-> We have actually had several soapUI users that provide comprehensive soapUI projects together with their web services, since it is a great way of giving a “platform-neutral” example of how the web service is supposed to work. Sometimes they also include a complete Mock Implementation of the web service in soapUI, which allows their client to build/test client code without having access to the actual live service

3) Anyhow, using JUnit as you describe is a great complement and as you say gives an insight in how the web service may be “perceived” by the client. Maybe we could add support for generating stubs for these kinds of JUnit testcases for JAX-WS from within soapUI?

rock on!

kind regards,

/Ole
eviware.com

By: jon

jon — Mon, 30 Apr 2007 18:21:59 +0000

Excellent points! I enjoy your blog immensely. Keep up the great work!