New answers tagged web-service
Part of the issue with RESTful Web APIs is there really isn't a standard as of yet. If there is a WADL for the Web API than SoapUI will typically work well. If not, than you're going to spend as much time, if not more, using SoapUI to work with your system than you would with any of the slew of tools that either exist or can be custom created. I am ...
From functional point of view - yes. However if you considering performing load testing at some point I would start looking into starting web services testing automation with a tool which is capable of running requests in multithreaded manner like Grinder or Apache JMeter.
We use Postman for considerable basic testing during the early stages of development. We then have used Gatling (http://gatling.io/#/) to facilitate load, regression, and stress testing.
A lot of devs I know use PostMan, a Chrome app. I have written my own tool using .Net that allows me to use pre-formatted requests with a given type reflected from a .dll file. A REST client is like a browser. It makes a request and does something with the response (like printing out the JSON response).
You can check this great blog: http://www.softwaretestinghelp.com/web-services-api-testing-tool-soapui-tutorial-1/ Second you can check the free courses here: http://soapui-tutorial.com/
Top 50 recent answers are included