I have to automate REST API testing in my project and integrate it in to existing CI in jenkins.
I am about to start coding using REST-assured.However I happened to see SOAP UI REST tutorial and understand that there is a maven plugin in SOAP UI to help jenkins integration. Before I progress, just wanted to know if there is an obvious advantage to using SOAP UI over Rest-assured. I have to complete the automation of around 30 requests with complex JSON responses in about a month - including schema validation for responses.
I haven't used REST-assured, but I had a quick look and I see it's a java DSL for testing rest services. Given that it does what it says it does, here's my answer...
I've used SOAP UI for testing of web services. Generally, SOAP UI has been very good for manual testing, but I found it difficult for automated testing.
The main reason was that many of the file paths are hard corded into SOAP UI projects, and so a project referring to c:\development\myproject\wsdl\myservice.wsdl would suddenly not work on another developer machine at /dev/myproject/wsdl/myservice.wsdl.
I also found not being able to effectively edit the SOAP UI projects in intellij meant I was constantly alt-tabbing.
Yes, the soap ui maven plugin did work, but I found it cumbersome.
Note that I haven't used SOAP UI REST, just "normal" SOAP UI, but if your use case is purely to implement automated testing, and that the REST-assured framework does what it says, I would certainly recommend to use the DSL.