cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X

Importing test runs in Codebeamer through REST API

AarushiS
8-Gravel

Importing test runs in Codebeamer through REST API

Hi,

 

We have tried adding test cases in Codebeamer using REST API and Azure DevOps Pipeline and now we are trying to add test runs to the test cases through API but getting the below error-

{

    "exception": "IllegalArgumentException",

    "message": "Request must be a multipart request."

}

API used - POST /http://ip-address/cb/rest/xunitresults

I think we are missing something to the end points. It would be great if anyone could help.

 

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

Hi Alfonso, Thanks for your suggestion. Currently we have some change in plans and won't be going forward with this API. In future if needed, will surely raise a support ticket.

View solution in original post

5 REPLIES 5

Hi @AarushiS , the error seems to come from the way the request is crafted: in case it has a file, this usually has to be sent with the request as multipart. I believe threads like https://stackoverflow.com/questions/16015548/how-to-send-multipart-form-data-request-using-postman could help to get an idea, but this can also be asked in the Postman forums: https://community.postman.com/t/video-how-to-send-multipart-form-data-request-file/51517 

Hi Alfonso,

 

I have followed 1.14.37.4 Batch test result update part in the wiki - REST API (v1) (codebeamer.com) but we haven't added the file yet in the Postman, only the JSON script is added. Is it why it is creating such error ? 

 

@AarushiSI think the current topic requires a Support Ticket to discuss the scenario and the challenge fully. If you haven't raised it yet, please feel free to do so. We can later update this thread when the root cause and solution are clarified. Thanks in advance for your actions.

Hi Alfonso, Thanks for your suggestion. Currently we have some change in plans and won't be going forward with this API. In future if needed, will surely raise a support ticket.

@AarushiSThank you for the update. I marked your previous message as the "solution", please feel free to contact us through a Support ticket in the future in case you need more assistance on this topic.

Top Tags