UFT One and Azure DevOps Server or Services
Using UFT One on a Windows machine, the Microsoft CI system Azure DevOps Server or Services can trigger test runs from the local file system, ALM, or the ALM Test Lab module.
This section describes how to integrate UFT One with the Azure DevOps Server or Services (formerly known as Team Foundation Server (TFS)).
- The same instructions apply if you are still using TFS.
For the sake of simplicity, further mentions of Azure DevOps Server in the UFT One Help Center also refer to Azure DevOps Services.
Set up an Azure agent Windows machine
Set up an Azure agent, or slave machine that the Azure DevOps Server will use to run the UFT One 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 or as a service (using the Local System Account).
As an administrator, run run.bat to start the agent, and leave the window open.
To use the UFT One Azure DevOps extension, you must have the following installed:
|On the Azure DevOps server||
The UFT One Azure DevOps extension
Install this on the Azure DevOps server, where you must have Administrator privileges.
For details, see Install the UFT One Azure DevOps extension.
|On the agent machine||
Set up your UFT One agent machine to work with the UFT One Azure DevOps Server and install the UFT One extension on the server.
Agent machine set up
Perform the following steps on your UFT One agent machine to set it up to work with the UFT One Azure DevOps extension.
Navigate to the ADM-TFS-Extension GitHub repository releases page, and download the following files from the latest release into the folder that you want to use for the UFT One-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 One 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 One-Azure integration files to another location, make sure to update the value of the UFT_LAUNCHER system environment variable accordingly.
UFT One Azure DevOps extension installation
On the server machine, install the UFT One 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.
Note: If you are still using a TFS server: The latest version of the TFS extension is no longer available on Marketplace. You can download it from the ADM-TFS-Extension GitHub repository and install it on TFS from the local gallery.
The UFT One Azure DevOps extension now displays as a valid extension for the server, and can be used to run UFT One tests.
When a new version of the UFT One Azure DevOps extension is available, it is automatically updated in Azure DevOps.
To use this new version of the extension, you must manually update the folder containing the UFT One-Azure integration files on the agent machine:
Clear any existing content from the _work/_tasks folder.
Update the UFT One working folder:
- In the ADM-TFS-Extension GitHub repository releases page, download the UFT.zip file that matches your extension's version and unzip it.
- Replace the content of your UFTWorking folder with the newly downloaded content.
After you update the files on the agent machine, open any existing tasks in Azure DevOps and update the task version field to use the new version.
Note: Existing tasks can continue to use the previous extension version until you update the files.
UFT One and Azure DevOps Server integration procedures
Trigger UFT One tests using any of the following procedures:
- Use Azure DevOps Server or Services to trigger a local test
- Use Azure DevOps Server or Services to trigger a test saved in ALM
- Use Azure DevOps Server or Services to trigger tests from ALM Lab Management
When running tests stored locally, you can upload the test result information generated by UFT One to an Azure Storage location. This lets you access the results from the Azure DevOps portal.
To support uploading UFT One test results to Azure Storage, perform the following steps:
On your Azure agent machine
Install Windows PowerShell version 5 or later.
Tip: Windows 10 has this installed by default.
Install the Azure PowerShell module and sign in using the Connect-AzAccount command.
On Azure Portal:
Create an Azure Storage account.
Create a Resource Group.
Create a Container. Set your container access level to Blob, so that you can access the resources directly from Azure DevOps as soon as the pipeline finishes running.
In each pipeline that runs UFT One tests from the file system:
Define the following pipeline variables:
The name of the Storage Account you created for this purpose.
The name of the Resource Group.
|CONTAINER||The name of the Container.|
In the pipeline steps that runs your UFT One tests:
Specify that you want the UFT One results uploaded to storage, and specify the artifacts to upload. For details, see Run a test saved on your local machine.
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 One 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.