SoapUI Vs. Postman
I am currently using Postman with the Jetpacks upgrade. Has anyone used both and have any good argument for one over the other? I realize there is a VERY large contrast in price but that isn't an issue if the software provides decent ROI over Postman. I am doing a lot of API testing but I am curious how well the other aspects of SoapUI work as well. If I could get more test coverage switching I would be interested.
Thanks for the input.
Personally I'm more partial to using a straight Unit testing framework, API's are meant to be developer friendly and I think programming with it exposes usability issues from a programmer's perspective.
Originally Posted by Mike.B
I've not used the Jetpacks upgrade. But my understanding is SoapUI from presentations that were given to me is that they offer additional workflows around testing rest services such as paramaterization, data-driven-testing, and service simulation. For Soap, you get lots of auto discovery features via WSDL. And it's able to work with a larger range of protocols. (i'm not sure how common those other protocols are)
I think SOAPUI is built on eclipse so you can also benefit from many plugins out there. I especially like code quality, debugging, and refactoring help plugins.
I also have used SOAP in a purely web environment with WSDL and liked it.
Another SoapUI Con
The 'out of the box' reporting is not suitable for test evidence (IMO) and creating custom reporting could be simplified. Slicing & Dicing XML to create a simple report is not good.
I used SoapUI Pro v4.5 2 years ago and have just started with SoapUI NG Pro. Some of the drap & drop advances have simplified some of the common tasks, the reporting needs to go this way too.