help

2 Topics

Result of "Clone Request" creates a second "linked" instance, rather than a new standalone version
I must be misunderstanding something, but here goes. I've created a REST request, including method, endpoint, resource, and Auth(!) for a particular call. I run it and it works fine. Now, there are say 30 more requests I need to create, each which varies only by the Resource (everything else is the same). Right clicking the Request that I just created, I see "Clone Request" (as one would expect), so I'm thinking "great, creating these 30 requests, each of which varies only slightly (the Resource) will be a breeze! However, when cloning a resource, I then discover that any alterations I make to it, *are also made in the original request that I cloned from*. This seems not very logical to me. I mean, perhaps there is some useful scenario for this behavior that I can't think of, but at the very least I would expect there to be an alternate clone method that creates a new Request that is not associated (will not alter) the original cloned Request. And another question I've always wondered about: I've attached a screenshot of the resource I am querying below. Does there happen to be some way I can "import" that resource and have all of the API calls automatically created in SOAP UI?
Solved
torevor 4 years ago Place ReadyAPI Questions
2.3KViews
0likes
4Comments
Request and Response URI different in Ready API and SoapUI NG Pro
Hi Guys, We are having an issue with the Ready API which is showing the Response URL different from the Request URI. This is the reason we are not able to switch to Ready API from SoapUI. We have analysed the traffic with Fiddler and our Response is originating from the URI that is mentioned in the Request Please find the screenshot for reference.
santhoshippili 5 years ago Place ReadyAPI Questions
2.4KViews
0likes
6Comments