UFT and Azure DevOps Server
The Microsoft CI system Azure DevOps Server can trigger tests using UFT from the local file system, from ALM, or from the ALM Test Lab module.
This section describes how to integrate UFT with the Azure DevOps Server (formerly known as Team Foundation Server (TFS)).
Tip: The same instructions apply if you are still using TFS.
Set up an Azure agent machine
Set up an Azure agent, or slave, machine that the Azure DevOps Server will use to run the UFT tests.
Download and configure an agent. For details, see Microsoft's instructions for creating self-hosted Windows agents.
When running config.cmd to configure the agent, choose to run the agent in interactive mode and not as an automatic service.
As an administrator, run run.bat to start the agent, and leave the window open.
To use the UFT Azure DevOps extension, you must have the following installed:
|On the Azure DevOps server||
The UFT Azure DevOps extension
Install this on the Azure DevOps server, where you must have Administrator privileges.
For details, see Install the UFT Azure DevOps extension.
|On the slave / agent machine||
Set up your UFT slave machine to work with the UFT Azure DevOps Server and install the UFT extension on the server.
Initial slave machine set up
Perform the following steps on your UFT slave machine to set it up to work with the UFT Azure DevOps extension. When you subsequently update the extension itself, you do not need to repeat all of these steps:
Download the following files from the ADM-TFS-Extension GitHub repository into the folder that you want to use for the UFT-Azure integration.
Run the Powershell unpack.ps1 script.
The script performs the following steps:
Unpacks the folder and files required for the extension and UFT agent to run. For example, you can see a UFT\UFTWorking folder.
Sets the UFT_LAUNCHER system environment variable. The variable's value should be the full path to the UFTWorking folder.
Caution: If, for any reason, you move the UFT-Azure integration files to another location, make sure to update the value of the UFT_LAUNCHER system environment variable accordingly.
UFT Azure DevOps extension installation
On the server machine, install the UFT UFT Azure DevOps extension, in one of the following ways:
|Install the extension directly from the Visual Studio Marketplace||
To locate the extension in the Marketplace, search for
|Install the extension from the local gallery||
Download the extension file (.vsix) from the ADM-TFS-Extension GitHub repository and save it locally.
Then install the extension from the local gallery.
For detailed steps on installing an Azure DevOps Server extension, see Microsoft's instructions for installing extensions.
The UFT Azure DevOps extension now displays as a valid extension for the server, and can be used to run UFT tests.
Additional steps when updating the extension
Each time you update the UFT Azure DevOps extension on the server, you must also update some files on the slave machine.
Perform the following steps in the folder that contains the files for the UFT-Azure integration:
Clear any existing content from the _work/_tasks folder.
Update the UFT working folder:
- Download the UFT.zip file from the ADM-TFS-Extension GitHub repository and unzip it.
- Replace the content of your UFTWorking folder with the newly downloaded content.
UFT and Azure DevOps Server integration procedures
Trigger UFT tests using any of the following procedures:
- Use Azure DevOps Server to trigger a local test
- Use Azure DevOps Server to trigger a test saved in ALM
- Use Azure DevOps Server to trigger a test from ALM Lab Management
Although any sensitive information is encrypted and encoded, Micro Focus encourages you to routinely remove unnecessary configuration files generated by your Azure DevOps Server builds, which are not removed by the Micro Focus UFT extension.
These are the files located in the UFTWorking\props folder.
By not implementing the file removal you may expose your system to increased security risks. You understand and agree to assume all associated risks and hold Micro Focus harmless for the same.
It remains at all times the Customer’s sole responsibility to assess its own regulatory and business requirements. Micro Focus does not represent or warrant that its products comply with any specific legal or regulatory standards applicable to Customer in conducting Customer's business.