How to investigate code regression using RTC
![]()
Hello to forum members,
This is a scenario I face during my work from time to time: a regression in our product is recognized by the QA team, they are able to mark the last known good build, so I can compare in RTC the two builds (the one where the regression was reported and the last known good build) and retrieve a list of submitted change-sets. I am wondering whether RTC has work-flow to offer for the next steps. Currently, what I do is to track the suspicious change-sets, look at their diffs, copy the previous state of the file, compile and check whether the regression disappears. Thanks, Gidi |
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.