von_bailey
Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: Authentication not being passed to header info.
Thanks for telling me what a link is on the internet. However, I was smart enough to figure that out on my own and saw that you had only sent me to the documentation that I used to find out how to use authentication in the first place. As my initial post says, the authentication was working and suddenly stopped working. Is THAT explained at the link that you supplied? I can't find it, so I ask what is on that page that addresses my issue? I'm not sure if you're purposely being rude or you truly feel I'm not bright enough to look at documentation or know what a link is on the internet. I will say I've had better interactions with SmartBear's "experts" in the past.Authentication not being passed to header info.
For some reason, the authentication is not being sent with my request. The username and password are filled out in the authrization aspect (see image) but there is no authorization in the header. What would cause this? It worked fine last week, but suddenly stopped sending the authorizatoin info yesterday. I've been looking for someone else having the same issue and cannot find anything.Re: Missing JSON in Request
Just had a dialog with a co-worker and he noticed something that I hadn't. The request is not showing the JSON because it is sending a "GET" instead of a "POST". As you can see in the image, the method is defined as a POST, but the Raw Request is saying that it is sending a GET. What would confuse the application in this manner?Re: Missing JSON in Request
Not unless the Raw Request window works differently than it does in the licensed version of SoapUI, which does show the JSON in the Raw Request window. Are you saying it's the norm in the non-licensed version not to display the JSON in the Raw Request window? Regardless, the problem is that when it doesn't show up in the Raw Request window, I get an error referencing the JSON. {"error": "Content-Type header missing (use Content-Type: application/json)"} Since the Content-Type header is not missing I have to assume the error is not referencing that directly. When the JSON does show up in the Raw Request Window(in the licensed version) the request does not create an error. I have to assume that the lack of the JSON in the request (which, aside from a failed request is the only difference from the licensed version) is the cause of the issue.Missing JSON in Request
I have created a project in SoapUI which, once a test case has completed, it hooks into TestRails and updates test case results. However, this process means that JSON must be sent with the request to pass the values of the test results. My problem seems to be that the SoapUI doesn't include the JSON in the request. See video at: http://screencast.com/t/pSessK4tSO As the video shows, the JSON is formatted correctly and the Media Type is set correctly, yet the request does not include the body.SoapUI integration with TestRails
Attempting to integrate test results into TestRails. Here's the request: "POST https://xxx.com/index.php?/api/v2/add_result_for_case/:RXXX/:CXXXX HTTP/1.1" Where:RXXX is the Run ID and CXXXX is the test case ID in TestRails I keep getting the following error. {"error":"External auth: Authenticated successfully, but no TestRail user was found for the given account."} I am entering my credentials vai teh Auth tab using Basic Authentication type so I don't understand the error. .
