Skip to main content
M
MaZa4-Participant
4-Participant
November 25, 2024
Question

How to create TestRuns for specific Version/Baseline of a TestSet/TestCases via REST-API

  • November 25, 2024
  • 2 replies
  • 731 views

Hi there,

 

as far as I can tell there is no documented way of providing a baseline or version number when calling

 

POST /v3/trackers/{testRunTrackerId}/testruns

 

Also the documentation https://codebeamer.com/cb/wiki/12709331#section-Creating+a+test+run does not give any hint as to how declare a baseline or version.

 

Am I missing something here or is this not possible?

 

I was even thinking of creating the testruns on head-revision first and then go and alter the link via

 

PUT/v3/associations/{associationId} 

 

But I found one article that seems to be somewhat related: https://www.ptc.com/en/support/article/CS413289 

 

My takeaway: TrackerItemReferenceModel does NOT support specific baseline/version addressing.

I assume that this actually goes for any API Endpoints the somehow require specific addressing. Is this right?

2 replies

Catalina
CatalinaCommunity Manager
Community Moderator
November 29, 2024

Hi @mz_01_10195112 

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant. It sometimes helps to have screenshots to better understand what you are trying to do.

 

Best regards,

Catalina | PTC Community Moderator
    M
    MaZa4-ParticipantAuthor
    4-Participant
    December 9, 2024

    Hi there

     

    to further elaborate on this I want to point out that the documentation actually has a hint to such a feature:

    https://codebeamer.com/cb/wiki/95044#section-Initiating+Test+Runs  

    Quote:

     You can also create a Test Run from a baselined version of a Test Set.

    I still can't believe that there is no viable option to do this via API.

     

    Any hints are welcome.

    Terms & ConditionsCookie settingsAccessibility statement