Baselines and Libraries not capturing changes to UFT scripts and scripted components.
Question ID: 107396

Using Baselines and Libraries we did a small change in the code of one scripted component which was part of the new baseline and then tried to compare the baseline with current entities. We were expecting this feature to show us which entity was changed but it did not capture any change and the comparison between the current entities and the baseline did not show any changes to synchronize.

Why is this happening while comparing current entities with the existing baseline?

Marked as spam
Posted by (Questions: 100, Answers: 5)
Asked on January 25, 2017 4:47 pm
Answers (1)
Private answer

Currrently the Baselines and libraries feature does not pick up ''script only changes'' to UFT and scripted components. Baselines and Libraries only detect changes at the database level, the scripts are stored in the repository, to determine script changes the baseline comparison would need to open every script in the repository for that baseline to check for changes to the code which would make the baseline comparison take a very long time. Someone has put in an Enhancement Request for this feature to be included in future versions but that enhancement request was deferred which means they do not plan on changing how this works. The change request is QCCR1J85181

A good way to make sure that this change is picked up is to get the users in the habit of editing a field on the item in ALM that shows when the most recent change was made and who made it, basically a ''change log'' field that way that field will get picked up in the comparison like a change to any other field.

Marked as spam
Posted by (Questions: 0, Answers: 364)
Answered on January 25, 2017 4:48 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top