Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE
Absent Member.. brickpattern Absent Member..
Absent Member..

UFT scripts - GIT to ALM

We got UFT automation scripts uploaded into ALM. As part of the test setup, we got Test Resources (excel data sheet) and the UFT script code associated to each test case. We also have the UFT script checked into GIT for version control and colloboration purposes.

The problem - each time a developer changes the code for any of the script in GIT, another person has to sync up the code in ALM.  For administrative purposes, the roles were kept seperate. 

Question- What is a best practice to upload the code from GIT to ALM , preferably automate the process? Is there a particular structure we have to maintain in code (GIT) that would allow us to do a single upload activity ? What are you thoughts...


Labels (1)
2 Replies
Sugey_S_QC Absent Member.
Absent Member.

Re: UFT scripts - GIT to ALM



For the moment we do not have a best practices for that howevere you can integrate GIT with ALM using ALI. See ALI information




Sue Sevilla | SW Technical Support Consultant.

Application Lifecycle Management



If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.

If you are satisfied with anyone's response please remember to give them KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation."





New Member.

Re: UFT scripts - GIT to ALM



We are in the same situation, what we have decided to so far is to have on ALM/QC only a launcher that does : 
LoadAndRun "C:/Path/UFT/Scenario"
And this action is associated with the right librairies in case of need global variable.
Which permits us to have git and alm separeted and maintains only one version of code.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.