Overall Satisfaction with SoapUI Pro
We use SoapUI Pro to cover automated, functional testing of our web services (SOAP/XML and REST/JSON primarily). It is used to the greatest extent in the QA department, but other client implementation teams also use some of it's basic functionality. Some of the key features we use are data source linking, Groovy scripting, and composite projects to facilitate our needs. It enables us to provide better coverage of expected results.
- Ease of use and setup, particularly with SOAP services where you have the WSDL. Import and go. If your WSDL changes you can update the definition or refactor it, which is a life saver.
- Decent GUI - I feel the GUI is well thought out in most areas.
- Scripting and Plugins - Allows setting of a script repository (Pro). In general, you can script in Groovy or JavaScript throughout a project. We use Groovy and haven't run into anything we haven't been able to find a solution to through scripting. For plugins, we've written some custom ones in Java to add menu items. To use them you just have to drop the jar file in a specific directory.
- Community - The community via blogs and forums is great. If you run into issues you can normally find someone else who had a similar problem. The response on the forums from SmartBear is also good. They also recently added an 'API Dojo' which is very informational.
- REST - They have come a long way, but there could still be improvements here. I find the learning curve much higher and not as straight forward using REST vs SOAP.
- Composite Projects - I'd really like to see them implement something around saving/refreshing Test Suites when using the Composite project ability in Pro. This is currently an enhancement in feature backlog (see their forum for more details). Functionality around Projects and Test Cases seems pretty sound.
- Less defects make it out of test environments
- Low Cost on Licensing