Skip to main content
A
AarushiS12-Amethyst
12-Amethyst
June 19, 2024
Solved

Importing test runs in Codebeamer through REST API

  • June 19, 2024
  • 1 reply
  • 2308 views

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!

Best answer by AarushiS

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.

1 reply

A
alfonso_c14-Alexandrite
14-Alexandrite
June 19, 2024

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 

    A
    AarushiS12-AmethystAuthor
    12-Amethyst
    June 19, 2024

    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 ? 

     

      A
      alfonso_c14-Alexandrite
      14-Alexandrite
      July 15, 2024

      @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.

      Terms & ConditionsCookie settingsAccessibility statement