Integrate UFT One with Azure DevOps - WordPress.com

Integrate UFT Onewith Azure DevOps

Step-by-step Guide

Integrate UFT One with Azure DevOps

Configure Self-hosted Windows Agent

Download UFT Extensions on the Self-Hosted Windows Agent

Install UFT One Plugin on Azure DevOps & Run Pipeline

Troubleshooting

Setup Self-hosted Windows Agent

Pre-requisite: Setup Self-hosted Windows Agent

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops

Step 1: Generate

New Token in Azure DevOps

Step 2: Create &

Download a New Agent

Step 3: Unpack

Agent to a Directory

Step 4: Run the

config.cmd

Step 5: Enter URL of your

Azure DevOps Tenant

Step 6: Enter your

Personal Access Token

Step 7: Choose the

Pool to register the

agent

Step 8: Enter Agent Name

Step 9: Enter your _work

folder

Step 10: Decide how to run the

agent

Step 11: Complete setup for

Agent

Step 12: Check your

Agent is online

Download UFT Extensions on the Self-Hosted

Windows Agent

Step 1: Download

UFT Extensions

Step 2: Unzip UFT.zip into the agent

folder

Step 3: Set the Environment

Variable UFT_LAUNCHER to

point on the UFTWorking folder

Install UFT One Plugin

Step 1: Get UFT Plugin from Azure

DevOps Marketplace

Step 2: Search for „UFT“ in the Azure DevOps

Marketplace

Step 3: Get the Plugin

downloaded into your Azure

DevOps environment

Step 4: Install the UFT

Plugin on your Azure DevOps

Tenant

Step 5: Proceed to your Azure

DevOps tenant

Step 6: Go to your Azure

DevOps Pipeline

Step 7 – Edit your Pipeline

Step 8: Add a new Testing Task to your

Pipeline

Step 9: Select the

appropriate UFT Task

Step 10: Configure the Tasks accordingly

Folder with UFT One Tests Location of UFT One Tests entered in Azure DevOps

Step 11: Add another Task

for UFT Reports

Step 12: Save your Pipeline

Step 13: Run Your Azure

DevOps Pipeline

Step 14: View UFT

One Results in Azure DevOps

Troubleshooting

If you see this error in the pipeline execution [ERR] System.IO.FileLoadException: Could not load file or assembly …\PSModule.dll, then unblock file in properties