RQM REST API - PUT Request
2 answers
Please try using the HTTPRequester/Poster Firefox plug-ins. Also, what is the response content with the 400 (Bad Request) response? See https://jazz.net/wiki/bin/view/Main/RqmApi#Troubleshooting for more details.
Comments
Hi Paul,
If you are using Firefox, bear in mind that there can be only one user actively connected to CLM. You need to log out a user before logging in as another user.
Donald, I am using RQMUrlUtility. The user credentials are provided as arguments.
Liora, the 412 (Precondition Failed) response code indicates something is missing in the PUT request. Can you try using the HttpRequester/Poster Firefox plug-in and post the response content?
Paul, tried using the HttpRequester/Poster Firefox plug-in. I am trying to figure out how to work with it.
Comments
Liora, this DEBUG log message does not indicate the cause of the 412 (Precondition Failed) response code. You need to capture the response content to resolve the reason. Please follow the instructions in https://jazz.net/wiki/bin/view/Main/RQMUsingPoster to use Poster.
I have followed the instructions and succeed working with Poster.
I have added the header and it worked. It doesn't work with the RQMUrlUtility.
Please open a RQM defect and we will fix the RQM URL Utility.
1 vote
Comments
Donald Nong
Oct 28 '14, 7:54 p.m.Can you please be more specific how you use the PUT method? I can use PUT against the resource URI to update attributes of a test artifacts without any errors. For example, below is the response body, along with HTTP 200 code, that I get when updating the title of a test case result.
P.S. Testing done with RQM 5.0.1.Liora Milbaum
Oct 28 '14, 10:05 p.m.Well, I am receiving the XML representation of the Test Result with the GET command, updating the XML file (changing the state from one state to another) and than issuing a PUT command with this XML.
Donald Nong
Oct 28 '14, 11:07 p.m.The <rqm:resultExternalId> is only in the response body, not in the request that I sent. The payload only contains <rqm:title> in my test. Also I was using a REST client to do the test, not RQMUrlUtility.
Umh...when I think about it, is it because you upgraded from 4.0.4 to 5.0.1 and I have a brand new 5.0.1 environment?