Crazy_Chris
Occasional Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Passing a dynamic authentication token
I have not been able to figure out any meaningful way to set any default values other than static ones from the project side, it cannot be a static value as the access_token refreshes x times an hour so it needs to be gathered from the Test that runs it. There is as far as I can tell no way to link from the project side to the test side to gather information. You can use get data but you can only set new properties with static values as far as I can tell from the project parameters. On a site note. Just recovering from a problem with all of the Git settings getting deleted without my knowledge, and 2 days ago when I had a conflict with one project file stating it was in use nothing had been pushed up for a month. Of course SoapUI didn't give any error message that the Repository URL was empty, something I would assume it would do when I click OK on "share changes through VCS"...This is not relevant to this thread really, just stating that I haven't had a chance to look further into the parameterizing issue because I just solved this 30 mins ago.11KViews0likes1CommentRe: Passing a dynamic authentication token
Hi PaulMS and thanks for your examples. What I really would like is to parameterize the header value and resource path in the same way, but under the Projects structure and not on every single Test under the SoapUI structure. But I cannot seem to get to any of the data elements that way. Right now I am building a testsuite that will be included in an automated build pipeline to do a health check of all the services, so it works even though the scope right now is small. But I see problems when something changes that I have to manually edit every single value on each Test affected as the values are not defined in the Project/Library, but as a reference in each Test to the value extracted. I might have done this wrong but I cannot for the life of me figure out anyway to accomplish this in Project/Library section or one place in a Test to pass the the rest of the Tests in that TestCase/TestSuite.11KViews0likes3CommentsRe: Passing a dynamic authentication token
Hi dasjestyrm, Although this is somewhat late, I would like to thank you for the proposed solution. This was just was I was after! Simple, short and to the point :) To Smartbear: Although I have to say that it seems unnecessary difficult to achieve this. Why can't I use get data to the element in another test and extract the fields that way without going through (although rather simple and short) groovy script to define new values and then use Get Data that is somehow able to extract the same information I wanted in the first place... This makes zero sense from a user perspective, why are headers and ressources excluded or limited with what data can be retrieved? It's obviously there, or it would be impossible even through a groovy script.11KViews0likes5CommentsRe: Change a Test Rest Request's link to project's request? "Open Request Editor"
Hello PaulMS, Thank you for the input. I looked at this again but could not see a way to add data from a dynamic value received from a POST or GET request. As mentioned I could create a static list from one of the format types(xml, cvs, json) and in each test, call the same values, but ideally I'd like to call a random value that is newly generated/created. And I cannot figure out how to pass these values to parametrize the request path. As I see it, these parameters need to be created and stored beforehand. I will admit that I am quite new to Soap, so if I am mistaken if an example could be made I'd really appreciate the assistance. Thanks! -- Chris2.3KViews0likes1CommentRe: Change a Test Rest Request's link to project's request? "Open Request Editor"
Thank you Bill_In_Irvine, This is a start, I will look into if your suggestions will work. I was hoping it would be simpler way to just add to an URL but I might think in the wrong direction and just work it out through the testcase as per your suggestion. It would be possible to just get a set of static values in an excel list to read from, but I was hoping to improve the test by getting fresh data.2.3KViews0likes3CommentsRe: Change a Test Rest Request's link to project's request? "Open Request Editor"
So to add an example: Some REST requests are: GET myserver.com/{ID_user} PUT myserver.com/{ID_user} DELETE myserver.com/{ID_user} PATCH myserver.com/{ID_user} POST myserver.com/{ID_user}/verify GET myserver.com/{ID_user}/verify/{ID_number} PUT myserver.com/{ID_user}/verify/{ID_number} DELETE myserver.com/{ID_user}/verify/{ID_number} I tried to make a new REST services under the Projects tab to be able to run tests from SoapUI Pro to those endpoints. My initial thought was that I could then call these endpoints in test cases as part of a testsuite. How can I put the {ID_user} value in the URL of a REST resource endpoint to run testcases, it seems to only accept static values and I want to look up random users without predefinding them in a list. Tried setting up the Rest services like this: Endpoint: Ressource: Parameters: GET myserver.com/ {ID_user} Or is my approach totally off? :) If anyone has a better way to pull this off I'd love some input or another approach to dynamic URLs.2.3KViews0likes5CommentsChange a Test Rest Request's link to project's request? "Open Request Editor"
Hello, The problem is that we initially set up each project's Rest Service as a new element. Now we find that we should have had fewer elements and just add the Ressources etc under one if the endpoint is identical. In SoapUI Pro we have defined a project and several TestSuits each having several Testcases with several Rest Requests linking back to the project. But I cannot find anyway to change the link from the SoapUI window elements back to the project window elements, am I missing something here? :) Thanks for any help understanding this.2.4KViews0likes7Comments