The best part of the tool is its GUI which helps us to test the SOAP and the best point is its open source and freely available. Its functional testing as a part includes the drag and drop and performing complex scenarios. We can also perform security testing load testing at a single glance.We can maintain our tests with a few clicks. Its been used by various enterprise business services companies and are making their business work flow simplier

There is nothing least about this but this need to be upgraded and come up with few bug fixes sometimes the page gets slow in responding this need to brought and overcome in next editions and versions

IfI was given a choice to hire only manual testers, I will do this. Otherwise, I won't

This can be used by testers/business analysts who do not know how to code. You can still use Jenkins to invoke tests using API

Pro feature is not really needed if you can code. But if you are willing to learn their UI, it works good for everybody.

It helped me to achieve my project testing goals in time. No need to test API's one by one anymore. I have wrote test cases for all of my API's. I'm so satisfied with this tool. I just need a one click to execute my test cases.

This is my favorite web service testing tool (Rest and Soap Web Service). Beautiful and user friendly UI. I can execute test cases as batches. Reporting functions are also good. It's compatible with 'Groovy' language. Data parametrization is also very helpful when testing API's. It comes with major nun-functional testing types such as load testing, performance testing, stress testing, security testing. I have tested successfully more than 150 API's by using 'Soap UI'. Really helpful.

It's better if they can improve reporting functionalities in 'Soap UI' open-source edition. Nothing else. It's perfect.!

I use it to many purposes, but the mostly used (here in Brazil) is for "Nota Fiscal" webservices, because every now and then, they change something so you need to debug and see what is happening or how to implement the new or changed tags into your system. Here is when SoapUI becomes handy, it will help you track the response structure and values mor easily. I love it!

I like it because you learn how to use it very quickly, then you can get very much more productive by using SoapUI to create, test, debug and validate WebServices. You can explore resulting XML payload in a very convenient way, with expansible nodes.

There is nothing I don't like in SoapUI, really, it is a very good tool. If I have to suggest something to improve, maybe they could improve the connections management. When you use it the first time you can get confused and start creating connections every time you open the tool and try to get response from a previously viewed WebService. I guess it could be simpler by starting with a saved services list then show all the connections you already have for that service.