Hi Team, I have created a utility which will validate the saved response with new response for an api request how to achieve that 1) I will save the sample response which will be compared with res...
Hi,
You can already do this sort of thing in ReadyAPI.
There isn't a nice simple function(s) that let you define saved responses and validate against future tests and cherry pick values to assert, but you can do it yourself.
You can use Groovy in Groovy Script steps in between 'standard' test steps to pretty much do all of the above.
I've pretty much done all you've mentioned with Groovy script in between test steps.
When looking at Groovy, the most useful thing is the ability to call a Groovy class outside of SoapUI. I use this a lot. When I started using SoapUI (as it was) I wrote some Groovy that I used to assert a service response against db contents. This was great, until I realised that I'd need this script in almost every test I'd run against that service. That meant when the service and/or data was extended with new columns, I'd then have to update every test that contained my script assertion. This became a maintenance nightmare, until I found I can call a Groovy class that sits outside of SoapUI. I created a Groovy class to do my db assertions, I then had to update each test to call this external class. But now, if there any content changes to the service, all I have to do is update my external class and all my tests then 'just work'.
When building your solution, think about the above to see opportunities for calling shared checks, scripts, whatever, etc.