Known Issues - ALM version control
Relevant for: GUI tests and components, API testing, and business process tests and flows
This topic describes known issues about version control in ALM.
Disappearing comparison data
Sometimes, checkpoint and output value comparison information disappears from the bottom panes of the Asset Comparison Tool after refreshing it. This can occur if you do the following:
Open the Asset Comparison Tool to view a comparison.
Switch to the Object Repository Manager.
Modify any of the current comparison's checkpoints or output values.
Save your changes.
Switch back to the Asset Comparison Tool.
Refresh the Asset Comparison Tool.
Select the checkpoint or output value that you modified.
Workaround: If this occurs, close the Asset Comparison Tool, and then open it again after you save your changes.
Comparing two baselines
When comparing two baselines, if the only change in a resource is its association to a test or component, the Asset Comparison Tool does not indicate any change in the resource even though ALM may indicate that the resource is Modified.
Localized UFT One
When working with a localized installation of UFT One, selecting the View Sample Snapshot option in the UFT One Asset Comparison Tool opens a window containing a sample image of the selected element in UFT One. The image displays the English user interface.
Creating an API test in an ALM project
When you create an API test in an ALM project in UFT One, make sure to check in the generated version before you make any changes. Otherwise:
Asset Viewer does not display the auto generated test if you try to view it in Version History.
Other users are unable to load the test from UFT One if the test is checked out by the current user.
Unable to save and run an API test in UFT One
In ALM, a new data source must be checked in first by its creator before it can be viewed, accessed, and used by other users.
If an API test imports an Excel data source that was never checked in in ALM, the whole test becomes unusable to other users.