QTP vs SOAP UI

[qtp_nerd]

How different is SOAP UI tool from QTP. If one knows about QTP beforehand will it be easy for the person to learn SOAP UI.

[PeterKlim]

They are completely different tools. SopaUI does not test like QTP does where it opens the AUT and starts doing things to it. SOAPUI is more API and load testing.

[PeterKlim]

Plus, SOAPUI Pro is horrible and so is SmartBear. I do not recommend them. I recommend running away from them and NEVER look back!

[elwinwildschut]

SOAPUI versus HP UFT versus Powershell for SOAP/REST API testing have all their own pros and cons.
Powershell is powerfull with one line of code you import your wsdl and directly you have the power at your fingertips. So far not anything seen thats more quicker and nice part its on everyone's windows machines including servers.

(New-Object System.Net.WebClient).Proxy.Credentials =  [System.Net.CredentialCache]::DefaultNetworkCredentials
$url = "http://www.webservicex.net/globalweather.asmx?wsdl"
$webservicex = New-WebServiceProxy -Uri $url -namespace WebServiceProxy -Class GlobalWeatherSoap
$webservicex | gm
$webservicex.GetCitiesByCountry("Netherlands")

For HP UFT you have to know the context menu to send away simple xml's in 1-2 seconds otherwise you are compiling which quickly gives you 2-3 minutes delay. The nice flowchart you get as a present from HP UFT for your documentation. Developers probably do not like the VBScripting stuff which is rather outdated language but with power of dotnetfactory object you can also deal from VBScript with .NET namespaces.
SOAPUI is very intuitive when you start it but for the more complex things you have to use Groovy scripting.

[bklabel1]

elwinwildschut,
I am not familiar with SoapUI. Is Groovy the only language that works with it?
thanks,

Kevin

[jpulley3]

Wouldn't the more natural comparison to SOAPUI be HP Service Test instead of HP QTP?

[marce11us]

@jpulley3 - you are correct: however if it's api testing, UFT API testing is not too bad i think (i am still looking at it as where i work we use both ReadyAPI(SoapUI) and UFT).

However i think this is also purely down to choice of the employer/client as to what tool they are looking at and also how much they are willing to spend

[dlai]

Personally I don't think you'll gain much using an automation tool to test APIs over a straight unit testing framework.

My arguments for this is, unit testing frameworks are free,

you can choose any language, like the same one developers are using so they can use the tests to debug their system,

and straight code without overhead of an automation platform tends to be faster. You can run more in parallel with same memory and cpu power.

[a.irvine]

Wouldn't the more natural comparison to SOAPUI be HP Service Test instead of HP QTP?

Service Test no longer exists. It was superceded by UFT back at v11.5 (way back in 2012).
The name change from QTP to UFT is due to the inclusion of the feature set that used to belong to Service Test.

[bklabel1]

Alex,
I was about to answer the same information as you about Service Test merging into UFT.
Appreciated.
Thanks,
Kevin