CI/CD integrations user guide

Last updated Feb 13, 2026

UiPath Test

Typically, the UiPath Test task runs an existing test set on Orchestrator. Additionally, you can use it to pack, deploy, and run test cases by specifying the path to a UiPath test project.

After the task has finished execution, the test results are uploaded to the Test tab in Azure DevOps. You can specify the test results output path in a JUnit format.

Depending on the result, the build will be either marked as successful (all test cases are passed), or failed (at least one test case failed).

Configuration

Use the following table to configure the UiPath Test inputs.

Argument	Description
Display name (Required)	Enter a name for your task.
Choose a test execution method	Choose the test that you wish to execute: Execute test set: Specify and run an existing test set in Test Manager or Orchestrator. Execute tests in project: Specify a project, deploy the package and run the test cases.
Orchestrator connection (Required)	Configure the service connection to access UiPath Orchestrator services. You can configure a connection only for this step or use an existing global connection. For more information, see Configuring UiPath Orchestrator service connection.
Project key (only for Test Manager)	Specify the project key in Test Manager (also known as Project Prefix). Required when executing tests in Test Manager. Leave empty for Orchestrator Testing Module.
Input parameters	Specify the file path to a JSON input file, such as `Input\jobParameters.json`. Specify the `type` argument if you're creating new input arguments at the Test Set level. Otherwise, you can use `name` and `value`.
Test set (Required for Execute test set method)	The name or key shown for the Test Set you wish to execute. Ensure that the Test Set includes the most recent version of the Test Cases. If the Test Set isn't in the default folder, make sure to include the relevant folder name before it. For instance, use `AccountingTeam\TestSet`.
Test project path (Required for Execute tests in project method)	Specify the test project location that is going to be executed.
Environment (Required for Execute tests in project method)	If you use classic folders (deprecated), you need to define the environment where the packages are going to be deployed. You can use this field to create or update packages.You can use the following example to add your environments to this field, separated by a comma: `testingEnvironment, productionEnvironment`.
Orchestrator folder (Required)	Specify the folder where the process is being deployed. For classic folders (deprecated), you can use specific robot names. For modern folders, you can use specific user and machine names. To input subfolders make sure to input both the parent folder name and the name of the subfolder. For instance, use `AccountingTeam\TeamJohn`.
Test results output path	Specify the test results output path in JUnit format (e.g., `Output\testResults.json`).
Timeout	Specify the number of seconds to wait before the request times out.
Trace Level	Select the logging level from the dropdown list.
Attach Robot Logs	Select this option to attach INFO level logs from the executing Robot. By default, this is unselected. For more information, see Robot Logs.

docs image

YAML pipeline

You can preview a fully parsed YAML document for the UiPath Test.

Example: Execute test set from Orchestrator

- task: UiPathTest@6
  displayName: 'Run Orchestrator Test Set'
  inputs:
    testTarget: TestSet
    orchestratorConnection: 'uipath-orchestrator-connection'
    testSet: 'MobileAutomationTests'
    folderName: 'MobileAutomationTesting'
    testReportDestination: '$(Build.ArtifactStagingDirectory)\report.xml'
    timeout: 3600
    traceLevel: 'Information'
- task: UiPathTest@6
  displayName: 'Run Orchestrator Test Set'
  inputs:
    testTarget: TestSet
    orchestratorConnection: 'uipath-orchestrator-connection'
    testSet: 'MobileAutomationTests'
    folderName: 'MobileAutomationTesting'
    testReportDestination: '$(Build.ArtifactStagingDirectory)\report.xml'
    timeout: 3600
    traceLevel: 'Information'

Example: Execute test set from Test Manager

- task: UiPathTest@6
  displayName: 'Run Test Manager Test Set'
  inputs:
    testTarget: TestSet
    orchestratorConnection: 'uipath-orchestrator-connection'
    projectKey: 'PROJ'  # Test Manager project key (Project Prefix)
    testSet: 'TS-123'   # Test Manager test set key
    folderName: 'TestManagerFolder'
    testReportDestination: '$(Build.ArtifactStagingDirectory)\testmanager-results.xml'
    timeout: 3600
    attachRobotLogs: true
    traceLevel: 'Information'
- task: UiPathTest@6
  displayName: 'Run Test Manager Test Set'
  inputs:
    testTarget: TestSet
    orchestratorConnection: 'uipath-orchestrator-connection'
    projectKey: 'PROJ'  # Test Manager project key (Project Prefix)
    testSet: 'TS-123'   # Test Manager test set key
    folderName: 'TestManagerFolder'
    testReportDestination: '$(Build.ArtifactStagingDirectory)\testmanager-results.xml'
    timeout: 3600
    attachRobotLogs: true
    traceLevel: 'Information'

Example: Execute test project

- task: UiPathTest@6
  displayName: 'Run Test Project'
  inputs:
    testTarget: TestProject
    orchestratorConnection: 'uipath-orchestrator-connection'
    testProjectPath: '$(Build.SourcesDirectory)\MobileAutomationTests'
    folderName: 'MobileAutomationTesting'
    environment: 'TestingRobots'  # Required only for classic folders
    testReportDestination: '$(Build.ArtifactStagingDirectory)\test-results.xml'
    timeout: 3600
    traceLevel: 'Information'
- task: UiPathTest@6
  displayName: 'Run Test Project'
  inputs:
    testTarget: TestProject
    orchestratorConnection: 'uipath-orchestrator-connection'
    testProjectPath: '$(Build.SourcesDirectory)\MobileAutomationTests'
    folderName: 'MobileAutomationTesting'
    environment: 'TestingRobots'  # Required only for classic folders
    testReportDestination: '$(Build.ArtifactStagingDirectory)\test-results.xml'
    timeout: 3600
    traceLevel: 'Information'

Example: Test Manager with project execution

- task: UiPathTest@6
  displayName: 'Run Test Manager Project'
  inputs:
    testTarget: TestProject
    orchestratorConnection: 'uipath-orchestrator-connection'
    projectKey: 'PROJ'  # Test Manager project key
    testProjectPath: '$(Build.SourcesDirectory)\TestProject'
    folderName: 'TestManagerFolder'
    parametersFilePath: '$(Build.SourcesDirectory)\test-params.json'
    testReportDestination: '$(Build.ArtifactStagingDirectory)\tm-project-results.xml'
    attachRobotLogs: true
    timeout: 7200
    traceLevel: 'Verbose'
- task: UiPathTest@6
  displayName: 'Run Test Manager Project'
  inputs:
    testTarget: TestProject
    orchestratorConnection: 'uipath-orchestrator-connection'
    projectKey: 'PROJ'  # Test Manager project key
    testProjectPath: '$(Build.SourcesDirectory)\TestProject'
    folderName: 'TestManagerFolder'
    parametersFilePath: '$(Build.SourcesDirectory)\test-params.json'
    testReportDestination: '$(Build.ArtifactStagingDirectory)\tm-project-results.xml'
    attachRobotLogs: true
    timeout: 7200
    traceLevel: 'Verbose'