Contributions
Re: With "New REST Service from URL" I get an extra slash.
The value for #Project#basepath is calculated based on properties set on the command line by the testrunner. Typical might be: basepath = /service/stb/show/media/playist/4 I suppose I'll have to change my scripts to eliminate the slash on the front of the basepaths. :(7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes1CommentRe: When a resource has both GET and POST methods, I can't add POST to a TestCase
Example: I created a new TestSuite and a new REST method, as a POST, and gave it a URL of http://localhost:8080/playlist/findPlaylist So now I have an empty TestCase. I can edit the Endpoint to be ${#Project#Endpoint} but there's no way to edit the resource field to make it ${#Project#basepath}/findPlaylist. no luck.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes1CommentRe: When a resource has both GET and POST methods, I can't add POST to a TestCase
Thanks for the suggestion. This "creates a new REST service and a REST Request test step for it." When I specify the URL as ${#Project#Endpoint}${#Project#basepath}/resource it tells me I have an invalid URL. If I use a "real" URL, then edit the path later, it generates extra slashes that I can't remove. Grr.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews0likes2CommentsWith "New REST Service from URL" I get an extra slash.
Being unable to add a POST resource to a TestCase when both POST and GET methods are available, I've been working around it by attempting to add a New REST Service from a URL. Suppose I have a local instance of my test service at http://localhost:8080/service/resource I can create a POST request. Now I want to change the Endpoint to ${#Project#Endpoint} so I can run the test against multiple other deployments on the runway. I can do that with no problem. Now I want to change the basepath for the resource from "/service" to ${#Project#basepath}, which is likely to be /service/environment/organization/some/proxy/address/contract/version to which the resource is appended "/resource" If I edit the Resource Path from the Resource screen in the Project and change it to ${#Project#basepath} instead it turns it into /${#Project#basepath}. There is no method I can discover that does not prepend a slash onto the resource. When a TestCase is created, it becomes ${#Project#Endpoint}/${#Project#basepath}, and since my basepath always has a slash at the start, I get a double slash in the full URL. Now normally this is a purely aesthetic problem, because double slash in a URL path tends to be harmless. But my OCD in this matter beats at me incessantly. Mojo7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes4CommentsWhen a resource has both GET and POST methods, I can't add POST to a TestCase
I imported a Swagger definition to create a Project. Several of my REST resources have both GET and POST methods -- two different ways to pass in parameters. (I didn't write this API.) See this screenshot for example: When I attempt to add the POST version of the resource, it will only give me the GET version, with a list of request parameters. I can't change the method to POST. I've tried creating a "New REST service from URL" to manually accommodate the POST versions of requests, but that has its own problems, which I'll mention in a different post.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes4Comments