UiPath Test Manager
Overview
Planview Hub offers integration solutions to flow test artifacts such as test results, test steps, and their associated tests, test runs, test instances, and folder structures.
Please review the sections below to learn more about supported test scenarios using UiPath Test Manager.
UiPath Test Manager & Jira Xray
In this integration scenario, an epic is created in Xray. Hub will flow the epic into UiPath as a requirement. A test set and test cases are then created in UiPath and synchronized over to Xray. When the tester in UiPath begins running her tests, Hub will flow the test results and linked defects back over to Xray to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the Xray Test artifact, while including the test results and defects from the UiPath artifact. To do this, you'll need to configure the following integrations:
- UiPath Requirements <> Xray Epics
- UiPath Test Sets <> Xray Test Sets
- UiPath Test Cases <> Xray Tests
- UiPath Test Executions <> Xray Test Executions
- UiPath Test Case Logs -> Xray Test Runs
- UiPath Defects <> Xray Defects
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Location | URL | Location | N/A |
| Priority | Priority | Single Select | Blocker, Critical, High, Medium, Low |
| Status | Status | Single Select | New, To Do, In Progress, Done |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| None | Labels | Single Select | Allow unmapped field values to flow |
| Parent Artifact | Parent | Relationship | N/A |
| None | Parents | Relationships | N/A |
| None | Test Coverage | Relationships | N/A |
| None | Test Status | Single Select | Untested, Blocked, Failed, Passed, Retest |
| None | Alternate ID | String | N/A |
| None | Alternate URL | String | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
| None | Xray ID | String | N/A |
| None | Xray URL | String | N/A |
Test Steps
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Action | Action | String | N/A |
| Expected Result | Expect Result | String | N/A |
| Id | Id | String | N/A |
| Status | Status | Single Select | Passed, Failed, Not Completed |
UiPath
You will need to add the following custom fields to your UiPath instance:
| Name | Type |
|---|---|
| Xray ID | String |
| Xray URL | String |
Xray
You will need to add the following custom fields to your Xray instance:
| Name | Type |
|---|---|
| Test Manager ID | String |
| Test Manager URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Requirements
- UiPath Test Cases
- UiPath Test Case Logs
- UiPath Test Executions
- UiPath Defects
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Xray ID | Xray ID | |
| Xray URL | Xray URL | |
| Labels | Labels | |
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Xray ID | Xray ID | |
| Xray URL | Xray URL | |
| UiPath Test Executions | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| UiPath Test Case Logs | Result | Test Case Status |
| UiPath Defects | Name | Summary |
| Description | Description | |
| Link Label | Alternate ID | |
| Link | Alternate URL | |
| Priority | Priority | |
| Status | Status | |
| UiPath Test Sets | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Xray ID | Xray ID | |
| Xray URL | Xray URL |
Test Step Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Description | Action |
| Expected Result | Expected Result | |
| Id | ID |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Test Sets | Parent |
| UiPath Test Execution | Test Set | Parents |
| UiPath Test Case Logs | Test Execution | Parent |
| Test Case | Test Coverage |
Xray
For this integration scenario, you'll need to configure the following Xray collections:
Work Item Collections
- Xray Epics
- Xray Tests
- Xray Test Executions
- Xray Test Runs
- Xray Defects
- Xray Test Sets
Field Mapping
Map the following Xray fields to the model:
| Collection | Xray Field | Model Field |
|---|---|---|
| Xray Epics | Epic Name | Summary |
| Summary | Summary | |
| Description | Description | |
| Labels | Labels | |
| Priority | Constant Value | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Key | Xray ID | |
| URL | Xray URL | |
| Xray Tests | Summary | Summary |
| Description | Description | |
| Priority | Constant Value | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Key | Xray ID | |
| URL | Xray URL | |
| Xray Test Executions | Summary | Summary |
| Description | Description | |
| Priority | Constant Value | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Xray Test Runs | Status | Test Status |
| Xray Defects | Summary | Summary |
| Description | Description | |
| Priority | Priority | |
| Status | Status | |
| Alternate ID | Alternate ID | |
| Alternate URL | Alternate URL | |
| Xray Test Sets | Summary | Summary |
| Description | Description | |
| Priority | Constant Value | |
| Key | Xray ID | |
| URL | Xray URL | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL |
Test Step Field Mapping
Map the following Xray fields to the model:
| Collection | Xray Field | Model Field |
|---|---|---|
| Xray Tests | Test Step Action | Action |
| Id | Id | |
| Expected Result | Expected Result |
Relationship Specification
Configure the following relationship mappings:
| Collection | Xray Field | Model Field |
|---|---|---|
| Xray Tests | Parent Link | Parent |
| Xray Test Executions | tests | Parents |
| Xray Test Runs | Test Run Test Execution key | Parent |
| Test Run Test key | Test Coverage |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Requirements <> Xray Epics
- UiPath Test Sets <> Xray Test Sets
- UiPath Test Cases <> Xray Tests
- UiPath Test Executions <> Xray Test Executions
- UiPath Test Case Logs -> Xray Test Runs
- UiPath Defects <> Xray Defects
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Container Mirror/Artifact Routing | Test Step Flow |
|---|---|---|---|---|
|
UiPath Requirements <> Xray Epics |
Work Item Synchronization | Two-way Creation | UiPath <> Xray | N/A |
|
UiPath Test Sets <> Xray Test Sets |
Work Item Synchronization |
Two-way Creation | UiPath <> Xray | N/A |
|
UiPath Test Cases <> Xray Tests |
Work Item Synchronization | Two-way Creation | UiPath <> Xray |
One-way Flow Xray accepts test steps |
| UiPath Test Executions <> Xray Test Executions | Work Item Synchronization | Two-way Creation | UiPath <> Xray | N/A |
|
UiPath Test Case Logs -> Xray Test Runs |
Work Item Synchronization | Two-way Creation | UiPath <> Xray | N/A |
|
UiPath Defects <> Xray Defects |
Work Item Synchronization |
Two-way Creation |
UiPath <> Xray | N/A |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Configuration Requirement |
Test Steps Test Steps are supported, but you must select which direction you'd like test steps to flow during intial configuration. Test Case Log and Test Result integration can be bi-directional but status cannot be updated in UiPath due to an API limitation. |
Any supported repository version:
|
| Good to Know |
Defect Integration The Defect integration can be bi-directional, but there must be an associated Test Case Log. |
Any supported repository version: |
| Feature Unsupported |
Test Step Results Test Step Results are not supported. |
Any supported repository version: |
| Third Party API Limitation |
Test Case Log & Test Run Integration The Test Case Log and Test Run integration can be bi-directional but values cannot be specified in UiPath due to an API limitation. |
Any supported repository version: |
| Third Party API Limitation |
Test Execution Integration The Test Execution integration can be bi-directional but values cannot be specified in UiPath due to an API limitation. |
Any supported repository version: |
UiPath Test Manager & Microsoft Azure DevOps
In this integration scenario, an epic is created in Azure DevOps. Hub will flow the epic into UiPath as a requirement. A test set and test cases are then created in UiPath and synchronized over to Azure DevOps. When the tester in UiPath begins running her tests, Hub will flow the test results and linked defects back over to Azure DevOps to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the Azure DevOps Test Case artifact, while including the Test Results from the UiPath artifact. To do this, you'll need to configure the following integrations:
- UiPath Requirements <> Azure DevOps Epics
- UiPath Test Sets <> Azure DevOps Test Suites
- UiPath Test Cases <> Azure DevOps Test Cases
- UiPath Test Executions -> Azure DevOps Test Runs
- UiPath Test Case Logs -> Azure DevOps Test Results
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| Location | URL | Location | N/A |
| None | Test Cases | Relationships | N/A |
| Parent Artifact | Parent | Relationship | N/A |
| None | Parents | Relationships | N/A |
| None | Test Coverage | Relationships | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
| None | Azure DevOps ID | String | N/A |
| None | Azure DevOps URL | String | N/A |
UiPath
You will need to add the following custom fields to your UiPath instance:
| Name | Type |
|---|---|
| Azure DevOps ID | String |
| Azure DevOps URL | String |
Azure DevOps
You will need to add the following custom fields to your Azure DevOps instance:
| Name | Type |
|---|---|
| Test Manager ID | String |
| Test Manager URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Requirements
- UiPath Test Cases
- UiPath Test Executions
- UiPath Test Case Logs
Container Collections
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Name | Summary |
| Description | Description | |
| URL | Test Manager URL | |
| Key | Test Manager ID | |
| Azure DevOps URL | Azure DevOps URL | |
| Azure DevOps ID | Azure DevOps ID | |
| UiPath Test Sets | Name | Summary |
| Description | Description | |
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Azure DevOps ID | Azure DevOps ID | |
| Azure DevOps URL | Azure DevOps URL | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| UiPath Test Executions | Name | Summary |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Test Sets | Parent |
| UiPath Test Executions | Test Set | Parents |
| UiPath Test Case Logs | Test Execution | Parent |
| Test Case | Test Coverage | |
| UiPath Test Sets | Assigned Test Cases | Test Cases |
Azure DevOps
For this integration scenario, you'll need to configure the following Azure DevOps collections:
Work Item Collections
- Azure DevOps Epics
- Azure DevOps Test Cases
- Azure DevOps Test Runs
- Azure DevOps Test Results
Container Collections
- Azure DevOps Test Suites
Field Mapping
Map the following Azure DevOps fields to the model:
| Collection | Azure DevOps Field | Model Field |
|---|---|---|
| Azure DevOps Epics | Title | Summary |
| Description | Description | |
| Formatted ID | Azure DevOps ID | |
| URL | Azure DevOps URL | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Azure DevOps Test Cases | Title | Summary |
| Description | Description | |
| Formatted ID | Azure DevOps ID | |
| URL | Azure DevOps URL | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Iteration Path | Constant Value Based on Projects | |
| Area Path | Constant Value Based on Projects | |
| Azure DevOps Test Results | Configuration | Constant Value |
| Azure DevOps Test Runs | Summary | Summary |
| Azure DevOps Test Suites | Title | Summary |
| Description | Description | |
| State | Constant Value | |
| Iteration Path | Constant Value | |
| Area Path | Constant Value |
Relationship Specification
Configure the following relationship mappings:
| Collection | Azure DevOps Field | Model Field |
|---|---|---|
| Azure DevOps Test Cases | Parent | Parent |
| Azure DevOps Test Runs | Parent Test Plan | Parents |
| Azure DevOps Test Results | Parent Test Plan | Constant Value |
| Configuration | Constant Value | |
| Azure DevOps Test Suites | Test Cases | Test Cases |
| Parent Test Plan | Constant Value |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Requirements <> Azure DevOps Epics
- UiPath Test Sets <> Azure DevOps Test Suites
- UiPath Test Cases <> Azure DevOps Test Cases
- UiPath Test Executions -> Azure DevOps Test Runs
- UiPath Test Case Logs -> Azure DevOps Test Results
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Artifact Routing/Container Mirroring |
|---|---|---|---|
|
UiPath Requirements <> Azure DevOps Epics |
Work Item Synchronization | Two-way Creation | UiPath <> ADO |
|
UiPath Test Sets <> Azure DevOps Test Suites |
Container + Work Item Synchronization | Two-way Creation | UiPath <> ADO |
|
UiPath Test Cases <> Azure DevOps Test Cases |
Work Item Synchronization | Two-way Creation | UiPath <> ADO |
|
UiPath Test Executions -> Azure DevOps Test Runs |
Work Item Synchronization | Two-way Creation | UiPath <> ADO |
|
UiPath Test Case Logs -> Azure DevOps Test Results |
Work Item Synchronization | Two-way Creation | UiPath <> ADO |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Third Party API Limitation |
Test Steps Test steps are not supported in Azure DevOps. |
Any supported repository version: |
| Third Party API Limitation |
Status The Test Case Log and Test Result integration can be bi-directional but status cannot be updated in UiPath due to an API limitation. |
Any supported repository version: |
| Configuration Requirement |
Test Runs Test Runs in Azure DevOps can only be created on Automated Test Runs. |
Any supported repository version: |
| Third Party API Limitation |
Test Step Results Test step results are not supported in Azure DevOps. |
Any supported repository version: |
| Third Party API Limitation |
Status The Test Execution and Test Run integration can be bi-directional but status cannot be updated in UiPath due to an API limitation. |
Any supported repository version: |
UiPath Test Manager & Micro Focus ALM/QC
In this integration scenario, a requirement and test case is created in Micro Focus ALM/QC. Hub will flow the requirement and test case into UiPath. A test set and test cases are then created in UiPath and synchronized over to ALM. When the tester in UiPath begins running his tests, Hub will flow the test results back over to ALM to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the ALM Test Case artifact, while including the Test Results from the UiPath artifact. To do this, you'll need to configure the following integrations:
- UiPath Requirements <> ALM Requirements
- UiPath Test Cases <> ALM Tests
- UiPath Test Sets <> ALM Test Sets
- UiPath Test Cases -> ALM Test Instances
- UiPath Test Case Logs <> ALM Test Runs
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Location | URL | Location | N/A |
| Status | Test Status | Single Select | Untested, Blocked, Failed, Retest, Passed |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| None | Test Coverage | Relationships | N/A |
| Parent Artifact | Parent | Relationship | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
| None | ALM ID | String | N/A |
| None | ALM URL | String | N/A |
Test Steps
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Action | Action | String | N/A |
| Expected Result | Expect Result | String | N/A |
| Id | Id | String | N/A |
| Status | Status | Single Select | Passed, Failed, Not Completed |
UiPath
You will need to add the following custom fields to your UiPath instance:
| Name | Type |
|---|---|
| ALM ID | String |
| ALM URL | String |
ALM
You will need to add the following custom fields to your ALM instance:
| Name | Type |
|---|---|
| UiPath ID | String |
| UiPath URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Requirements
- UiPath Test Cases
- UiPath Test Case Logs
Container Collections
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Name | Summary |
| Description | Description | |
| Created | Created | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| ALM ID | ALM ID | |
| ALM URL | ALM URL | |
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Created | Created | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| ALM ID | ALM ID | |
| ALM URL | ALM URL | |
| UiPath Test Case Logs | Key | Test Manager ID |
| URL | Test Manager URL | |
| Result | Test Status | |
| UiPath Test Sets | Name | Summary |
| Description | Description | |
| Created | Created | |
| ALM ID | ALM ID | |
| ALM URL | ALM URL | |
| Key | Test Manager ID | |
| URL | Test Manager URL |
Test Step Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Description | Action |
| Expected Result | Expected Result | |
| Id | ID | |
| UiPath Test Case Logs | Description | Action |
| Expected Result | Expected Result | |
| Id | ID | |
| Result | Status |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Assigned Test Cases | Test Coverage |
| UiPath Test Cases | Test Sets | Parent |
| UiPath Test Case Logs | Test Case | Test Coverage |
Micro Focus ALM/QC
For this integration scenario, you'll need to configure the following ALM collections:
Work Item Collections
- ALM Requirements
- ALM Tests
- ALM Test Instances
- ALM Test Runs
Container Collections
- ALM Test Sets
Field Mapping
Map the following ALM fields to the model:
| Collection | ALM Field | Model Field |
|---|---|---|
| ALM Requirements | Name | Summary |
| Description | Description | |
| Creation Date | Created | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Formatted ID | ALM ID | |
| URL | ALM URL | |
| ALM Tests | Test Name | Summary |
| Description | Description | |
| Creation Date | Created | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Formatted ID | ALM ID | |
| URL | ALM URL | |
| ALM Test Instances | Name | Summary |
| Formatted ID | ALM ID | |
| URL | ALM URL | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| ALM Test Runs | Test Manager ID | Test Manager ID |
| Test Manager URL | Test Manager URL | |
| Test Status | Status | |
| Tester | Constant Value | |
| ALM Test Sets | Name | Summary |
| Description | Description | |
| Open Date | Created | |
| Formatted ID | ALM ID | |
| URL | ALM URL | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL |
Test Step Field Mapping
Map the following ALM fields to the model:
| Collection | ALM Field | Model Field |
|---|---|---|
| ALM Tests | Description | Action |
| Expected Result | Expected Result | |
| Step ID | Id | |
| Step Name | Summary | |
| Step Name | Step Name | |
| ALM Test Runs | Description | Action |
| Expected | Expected Result | |
| Step ID | Id | |
| Status | Status | |
| Step Name | Summary | |
| Step Name | Step Name |
Relationship Specification
Configure the following relationship mappings:
| Collection | ALM Field | Model Field |
|---|---|---|
| ALM Requirements | Test Coverage | Test Coverage |
| ALM Test Instances | Test | Parent |
| ALM Test Runs | Test Instance | Test Coverage |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Requirements <> ALM Requirements
- UiPath Test Cases <> ALM Tests
- UiPath Test Sets <> ALM Test Sets
- UiPath Test Cases -> ALM Test Instances
- UiPath Test Case Logs <> ALM Test Runs
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Test Step Flow | Container Mirror/Artifact Routing |
|---|---|---|---|---|
|
UiPath Requirements <> ALM Requirements |
Work Item Synchronization | Two-way Creation | N/A | UiPath <> ALM |
|
UiPath Test Cases <> ALM Tests |
Work Item Synchronization |
Two-way Creation | No Flow | UiPath <> ALM |
|
UiPath Test Sets <> ALM Test Sets |
Container + Work Item Synchronization | Two-way Creation | N/A | UiPath <> ALM |
|
UiPath Test Cases -> ALM Test Instances |
Work Item Synchronization |
One-way Creation ALM accepts new artifacts |
N/A | UiPath -> ALM |
|
UiPath Test Case Logs <> ALM Test Runs |
Work Item Synchronization |
Two-way Creation |
One-way Flow ALM accepts test steps |
UiPath <> ALM |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Configuration Requirement |
Test Steps Test Steps are supported, but you must select which direction you'd like test steps to flow during intial configuration. |
Any supported repository version:
|
| Third Party API Limitation |
Test Steps Test Steps are not supported in the Test Case/Test Instance integration due to an API limitation in ALM. |
Any supported repository version: |
| Good to Know |
Test Steps Test Steps can synchronize from UiPath to ALM in the Test Case Log/Test Run integration, however, these will not be the original test steps in ALM. A test execution in UiPath must be linked to a new test case log in order to create the test case log. |
Any supported repository version: |
| Configuration Requirement |
Test Case/Test Instance Integration An extension must be configured in the Test Case/Test Instance integration. Multiple custom fields must be created in UiPath to properly execute this integration. |
Any supported repository version: |
| Third Party API Limitation |
Test Results Due to an API Limitation in UiPath, test results can only flow in one direction. |
Any supported repository version: |
UiPath Test Manager & Micro Focus ALM Octane
In this integration scenario, a requirement is created in ALM Octane. Hub will flow the requirement into UiPath. A test set and test cases are then created in UiPath and synchronized over to ALM Octane. When the tester in UiPath begins running his tests, Hub will flow the test case logs over to ALM Octane and the tester in ALM Octane will report the defects backs to UiPath to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the ALM Octane Test artifact, while including the Test Case Logs from the UiPath artifact and Defects from the ALM Octane artifact. To do this, you'll need to configure the following integrations:
- UiPath Requirements <> Octane Requirements
- UiPath Test Sets <> Octane Test Suites
- UiPath Test Cases <> Octane Tests
- UiPath Test Case Logs -> Octane Runs
- UiPath Defects <- Octane Defects
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Location | URL | Location | N/A |
| Priority | Priority | Single Select | Blocker, Critical, High, Medium, Low |
| Status | Status | Single Select | New, To Do, In Progress, Done |
| None | Testing Status | Single Select | To Do, Executing, Pass, Aborted, Fail |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| None | Test Cases | Relationships | N/A |
| None | Related | Relationships | N/A |
| None | Test Coverage | Relationships | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
| None | Octane ID | String | N/A |
| None | Octane URL | String | N/A |
Test Steps
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Action | Action | String | N/A |
| Expected Result | Expect Result | String | N/A |
| Id | Id | String | N/A |
| Status | Status | Single Select | Passed, Failed, Not Completed |
UiPath
You will need to add the following custom fields to your UiPath instance:
| Name | Type |
|---|---|
| Octane ID | String |
| Octane URL | String |
ALM Octane
You will need to add the following custom fields to your ALM Octane instance:
| Name | Type |
|---|---|
| Test Manager ID | String |
| Test Manager URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Requirements
- UiPath Test Cases
- UiPath Test Case Logs
- UiPath Defects
Container Collections
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Name | Summary |
| Description | Description | |
| Status | Status | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Octane ID | Octane ID | |
| Octane URL | Octane URL | |
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Status | Status | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Octane ID | Octane ID | |
| Octane URL | Octane URL | |
| UiPath Test Case Logs | ID | Summary |
| Result | Testing Status | |
| UiPath Defects | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| Link Label | Octane ID | |
| Link | Octane URL | |
| Priority | Priority | |
| UiPath Test Sets | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Octane ID | Octane ID | |
| Octane URL | Octane URL |
Test Step Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Description | Action |
| Expected Result | Expected Result | |
| Id | ID |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Sets | Assigned Test Cases | Test Cases |
| UiPath Test Cases | Assigned To Requirements | Related |
| UiPath Test Case Logs | Test Case | Test Coverage |
| UiPath Defects | Test Case Log | Related |
ALM Octane
For this integration scenario, you'll need to configure the following Octane collections:
Work Item Collections
- Octane Requirements
- Octane Tests
- Octane Runs
- Octane Defects
Container Collections
- Octane Test Suites
Field Mapping
Map the following Octane fields to the model:
| Collection | Octane Field | Model Field |
|---|---|---|
| Octane Requirements | Name | Summary |
| Description | Description | |
| Phase | Status | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Formatted ID | Octane ID | |
| URL | Octane URL | |
| Octane Tests | Name | Summary |
| Description | Description | |
| Phase | Status | |
| Application module | Constant Value | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Formatted ID | Jama ID | |
| URL | Jama URL | |
| Octane Runs | Name | Summary |
| Native status | Testing Status | |
| Release | Constant Value | |
| Octane Defects | Name | Summary |
| Description | Description | |
| Priority | Priority | |
| Status | Status | |
| Formatted ID | Octane ID | |
| URL | Octane URL | |
| Phase | Constant Value | |
| Application modules | Constant Value | |
| Test Manager ID | Test Manager ID | |
| Octane Test Suites | Name | Summary |
| Description | Description | |
| Formatted ID | Octane ID | |
| URL | Octane URL | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Application modules | Constant Value |
Test Step Field Mapping
Map the following Octane fields to the model:
| Collection | Octane Field | Model Field |
|---|---|---|
| Octane Tests | Description | Action |
Relationship Specification
Configure the following relationship mappings:
| Collection | Octane Field | Model Field |
|---|---|---|
| Octane Requirements | Parent | Constant Value |
| Octane Tests | Covered requirement | Related |
| Octane Runs | Test | Test Coverage |
| Octane Defects | Runs | Related |
| Octane Test Suites | Contained Tests | Test Cases |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Requirements <> Octane Requirements
- UiPath Test Sets <> Octane Test Suites
- UiPath Test Cases <> Octane Tests
- UiPath Test Case Logs -> Octane Runs
- UiPath Defects <- Octane Defects
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Test Step Flow | Container Mirror/Artifact Routing |
|---|---|---|---|---|
|
UiPath Requirements <> Octane Requirements |
Work Item Synchronization | Two-way Creation | N/A | UiPath <> Octane |
|
UiPath Test Sets <> Octane Test Suites |
Container + Work Item Synchronization |
Two-way Creation | N/A | UiPath <> Octane |
|
UiPath Test Cases <> Octane Tests |
Work Item Synchronization | Two-way Creation |
One-way Flow Octane accepts test steps |
UiPath <> Octane |
|
UiPath Test Case Logs -> Octane Runs |
Work Item Synchronization | Two-way Creation | N/A | UiPath <> Octane |
|
UiPath Defects <- Octane Defects |
Work Item Synchronization |
Two-way Creation |
N/A | UiPath <> Octane |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Third Party API Limitation |
Test Steps Test steps are only supported one-way from UiPath in the Test Case/Test integration. |
Any supported repository version: |
| Configuration Requirement |
Run Suite Integration The Test Suites field must be set to a constant value in the Run Suite integration. |
Any supported repository version: |
| Third Party API Limitation |
Test Case Log & Run Integration The Test Case Log/Run integration is one-way due a limitation in UiPath. |
Any supported repository version: |
| Third Party API Limitation |
Defect Integration The Defect integration is one-way from Octane due to a limiation in UiPath. |
Any supported repository version: |
UiPath Test Manager & TestRail
In this integration scenario, a Test Section is created in TestRail. Hub will flow the Test Section into UiPath as a Test Set. A test case is then created in TestRail and synchronized over to UiPath. When the tester in TestRail begins running her tests, Hub will flow the tests back over to UiPath as test case logs to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the TestRail Test Case artifact. To do this, you'll need to configure the following integrations:
- UiPath Test Sets <> TestRail Test Sections
- UiPath Test Cases <> TestRail Test Cases
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| Location | URL | Location | N/A |
| Parent Artifact | Parent | Relationship | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
Test Steps
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Action | Action | String | N/A |
| Expected Result | Expected Result | String | N/A |
| Id | Id | String | N/A |
TestRail
You will need to add the following custom fields to your TestRail instance:
| Name | Type |
|---|---|
| Test Manager ID | String |
| Test Manager URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Test Cases
Container Collections
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| UiPath Test Sets | Name | Summary |
| Description | Description |
Test Step Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Description | Action |
| Expected Result | Expected Result | |
| Id | Id |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Test Sets | Parent |
TestRail
For this integration scenario, you'll need to configure the following TestRail collections:
Work Item Collections
- TestRail Test Cases
Container Collections
- TestRail Test Sections
Field Mapping
Map the following TestRail fields to the model:
| Collection | TestRail Field | Model Field |
|---|---|---|
| TestRail Test Cases | Title | Name |
| Preconditions | Description | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| Template | Constant Value | |
| TestRail Test Sections | Name | Summary |
| Description | Description | |
| ID | Formatted ID |
Test Step Field Mapping
Map the following TestRail fields to the model:
| Collection | TestRail Field | Model Field |
|---|---|---|
| TestRail Test Cases | Step Description | Action |
| Expected Result | Expected Result |
Relationship Specification
Configure the following relationship mappings:
| Collection | TestRail Field | Model Field |
|---|---|---|
| TestRail Test Cases | Section | Parent |
| Test Suite / Baseline | Constant Value | |
| TestRail Test Sections | Test Suite / Baseline | Constant Value |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Test Sets <> TestRail Test Sections
- UiPath Test Cases <> TestRail Test Cases
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Artifact Routing/Container Mirroring | Test Step Flow |
|---|---|---|---|---|
|
UiPath Test Sets <> TestRail Test Sections |
Container + Work Item Synchronization |
Two-way Creation | UiPath <> TestRail | N/A |
|
UiPath Test Cases <> TestRail Test Cases |
Work Item Synchronization | Two-way Creation | UiPath <> TestRail |
One-way Flow TestRail collection accepts Test Steps |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Third Party API Limitation |
Test Steps Test Steps on a Test Case are read-only and can only synchronize from TestRail to UiPath. |
Any supported repository version: |
| Third Party API Limitation |
Test Results Test Results are read-only and cannot be synchronized from TestRail or UiPath. |
Any supported repository version: |
UiPath Test Manager & Jama
In this integration scenario, a requirement is created in Jama. Hub will flow the requirement into UiPath. A test set and test cases are then created in UiPath and synchronized over to Jama. When the tester in UiPath begins running his tests, Hub will flow the test results and linked defects back over to Jama to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the Jama Test Case artifact, while including the Test Results from the UiPath artifact. To do this, you'll need to configure the following integrations:
- UiPath Requirements <> Jama Requirements
- UiPath Test Sets <> Jama Test Set Folders
- UiPath Test Cases <> Jama Test Cases
- UiPath Test Case Logs -> Jama Test Results
- UiPath Defects <- Jama Defects
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Location | URL | Location | N/A |
| Priority | Priority | Single Select | Blocker, Critical, High, Medium, Low |
| Status | Status | Single Select | New, To Do, In Progress, Done |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| None | Test Coverage | Relationships | N/A |
| None | Related | Relationships | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
| None | Jama ID | String | N/A |
| None | Jama URL | String | N/A |
Test Steps
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Action | Action | String | N/A |
| Expected Result | Expect Result | String | N/A |
| Id | Id | String | N/A |
| Status | Status | Single Select | Passed, Failed, Not Completed |
UiPath
You will need to add the following custom fields to your UiPath instance:
| Name | Type |
|---|---|
| Jama ID | String |
| Jama URL | String |
Jama
You will need to add the following custom fields to your Jama instance:
| Name | Type |
|---|---|
| Test Manager ID | String |
| Test Manager URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Requirements
- UiPath Test Cases
- UiPath Test Case Logs
- UiPath Defects
Container Collections
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Jama ID | Jama ID | |
| Jama URL | Jama URL | |
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| Jama ID | Jama ID | |
| Jama URL | Jama URL | |
| UiPath Test Case Logs | Key | Test Manager ID |
| URL | Test Manager URL | |
| UiPath Defects | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| Priority | Priority | |
| Status | Status | |
| UiPath Test Sets | Name | Summary |
| Description | Description |
Test Step Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Description | Action |
| Expected Result | Expected Result | |
| Id | ID | |
| UiPath Test Case Logs | Description | Action |
| Expected Result | Expected Result | |
| Id | ID | |
| Result | Status |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Assigned To Requirements | Related |
| UiPath Test Case Logs | Test Case | Test Coverage |
Artifact Union
Configure the following artifact union:
| Collection | Relationship Field | Union Artifact Types | Flow Test Steps From |
|---|---|---|---|
| UiPath Test Case Logs | Test Case | Test Case | This Collection |
Jama
For this integration scenario, you'll need to configure the following Jama collections:
Work Item Collections
- Jama Requirements
- Jama Test Cases
- Jama Test Results
- Jama Defects
Container Collections
- Jama Test Set Folders
Field Mapping
Map the following Jama fields to the model:
| Collection | Jama Field | Model Field |
|---|---|---|
| Jama Requirements | Name | Summary |
| Description | Description | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| ID | Jama ID | |
| URL | Jama URL | |
| Jama Test Cases | Name | Summary |
| Description | Description | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| ID | Jama ID | |
| URL | Jama URL | |
| Jama Test Results | Test Manager ID | Test Manager ID |
| Test Manager URL | Test Manager URL | |
| Jama Defects | Name | Summary |
| Description | Description | |
| Priority | Priority | |
| Status | Status | |
| Test Manager ID | Test Manager ID | |
| Jama Test Folders | Name | Summary |
| Description | Description |
Test Step Field Mapping
Map the following Jama fields to the model:
| Collection | Jama Field | Model Field |
|---|---|---|
| Jama Test Cases | Notes | Summary |
| Action | Action | |
| Expected Result | Expected Result | |
| Jama Test Results | Notes | Summary |
| Action | Action | |
| Expected Result | Expected Result |
Relationship Specification
Configure the following relationship mappings:
| Collection | Jama Field | Model Field |
|---|---|---|
| Jama Test Cases | Related to upstream | Related |
| Jama Test Results | Parent upstream | Test Coverage |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Requirements <> Jama Requirements
- UiPath Test Sets <> Jama Test Set Folders
- UiPath Test Cases <> Jama Test Cases
- UiPath Test Case Logs -> Jama Test Results
- UiPath Defects <- Jama Defects
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Container Mirror/Artifact Routing |
|---|---|---|---|
|
UiPath Requirements & Jama Requirements |
Work Item Synchronization | Two-way Creation | UiPath <> Jama |
|
UiPath Test Sets & Jama Test Set Folders |
Container + Work Item Synchronization |
Two-way Creation | UiPath <> Jama |
|
UiPath Test Cases & Jama Test Cases |
Work Item Synchronization | Two-way Creation | UiPath <> Jama |
|
UiPath Test Case Logs & Jama Test Results |
Work Item Synchronization | Two-way Creation | UiPath <> Jama |
|
UiPath Defects & Jama Defects |
Work Item Synchronization |
Two-way Creation |
UiPath <> Jama |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Third Party API Limitation |
Status The Test Case Log and Test Result integration can be bi-directional but status cannot be updated in UiPath due to an API limitation. |
Any supported repository version:
|
UiPath Test Manager & Tricentis Tosca
NOTE
Please be aware that Tricentis Tosca refers to the Test Management server component within the Tosca server suite. It should not be confused with Tricentis qTest, which is a separate product offering.
In this integration scenario, a requirement is created in Tosca. Hub will flow the requirement into UiPath. A test set and test cases are then created in UiPath and synchronized over to Tosca. When the tester in UiPath begins running her tests, Hub will flow the test execution and linked defects back over to Tosca to maintain full visibility across the lifecycle.
The goal of this integration scenario is to synchronize the UiPath Test Case artifact with the Tosca Test Case artifact, while including the Test Executions and Defects from the UiPath artifact. To do this, you'll need to configure the following integrations:
- UiPath Requirements <> Tosca Requirements
- UiPath Test Sets <> Tosca Test Case Folders
- UiPath Test Cases <> Tosca Test Cases
- UiPath Test Executions <> Tosca Execution List Folders
- UiPath Defects <> Tosca Defects
Connect to your Repositories
First, connect to your repository by following the instructions here.
You can learn more about connector-specific configuration in our Connector Docs.
Set Up your Model
Review general details on creating or reusing a model.
For this integration scenario, you will need to add the following fields to your model:
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Summary | Summary | String | N/A |
| Description | Description | Rich Text | N/A |
| Formatted ID | Formatted ID | String | N/A |
| Location | URL | Location | N/A |
| Status | Status | Single Select | New, To Do, In Progress, Done |
| Created | Created | Date Time | N/A |
| Modified | Modified | Date Time | N/A |
| None | Parents | Relationships | N/A |
| None | Alternate ID | String | N/A |
| None | Alternate URL | String | N/A |
| None | Test Manager ID | String | N/A |
| None | Test Manager URL | String | N/A |
| None | Tosca ID | String | N/A |
| None | Tosca URL | String | N/A |
Test Steps
| Smart Field | Label | Type | Field Values |
|---|---|---|---|
| Action | Action | String | N/A |
| Expected Result | Expect Result | String | N/A |
| Id | Id | String | N/A |
| Status | Status | Single Select | Passed, Failed, Not Completed |
UiPath
You will need to add the following custom fields to your UiPath instance:
| Name | Type |
|---|---|
| Tosca ID | String |
| Tosca URL | String |
Tosca
You will need to add the following custom fields to your Tosca instance:
| Name | Type |
|---|---|
| Test Manager ID | String |
| Test Manager URL | String |
Create your Collections
You can learn general details on configuring collections here:
Review the details in the sections below to ensure that any required fields are mapped in your collections.
UiPath
For this integration scenario, you'll need to configure the following UiPath collections:
Work Item Collections
- UiPath Requirements
- UiPath Test Cases
- UiPath Test Executions
- UiPath Defects
Container Collections
- UiPath Test Sets
Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Requirements | Name | Summary |
| Description | Description | |
| Tosca ID | Tosca ID | |
| Tosca URL | Tosca URL | |
| UiPath Test Sets | Name | Summary |
| Description | Description | |
| Tosca ID | Tosca ID | |
| Tosca URL | Tosca URL | |
| UiPath Test Cases | Name | Summary |
| Description | Description | |
| Tosca ID | Tosca ID | |
| Tosca URL | Tosca URL | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| UiPath Test Executions | Name | Summary |
| Description | Description | |
| Key | Test Manager ID | |
| URL | Test Manager URL | |
| UiPath Defects | Name | Summary |
| Description | Description | |
| Status | Status | |
| Link Label | Alternate ID | |
| Link | Alternate URL |
Test Step Field Mapping
Map the following UiPath fields to the model:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Cases | Description | Action |
| Expected Result | Expected Result | |
| Id | ID |
Relationship Specification
Configure the following relationship mappings:
| Collection | UiPath Field | Model Field |
|---|---|---|
| UiPath Test Executions | Test Set | Parents |
Tosca
For this integration scenario, you'll need to configure the following Tosca collections:
Work Item Collections
- Tosca Requirements
- Tosca Test Cases
- Tosca Execution Lists
- Tosca Defects
Container Collections
- Tosca Test Case Folders
Field Mapping
Map the following Tosca fields to the model:
| Collection | Tosca Field | Model Field |
|---|---|---|
| Tosca Requirements | Name | Summary |
| Description | Description | |
| Formatted ID | Tosca ID | |
| URL | Tosca URL | |
| SynchronizationPolicy | Constant Value | |
| Tosca Test Cases | Name | Summary |
| Description | Description | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| ID | Tosca ID | |
| URL | Tosca URL | |
| SynchronizationPolicy | Constant Value | |
| Tosca Execution List Folders | Name | Summary |
| Description | Description | |
| Test Manager ID | Test Manager ID | |
| Test Manager URL | Test Manager URL | |
| SynchronizationPolicy | Constant Value | |
| Tosca Defects | Name | Summary |
| Description | Description | |
| State | Status | |
| Formatted ID | Alternate ID | |
| URL | Alternate URL | |
| SynchronizationPolicy | Constant Value | |
| Tosca Test Case Folders | Name | Summary |
| Description | Description | |
| Formatted ID | Tosca ID | |
| URL | Tosca URL | |
| SynchronizationPolicy | Constant Value |
Test Step Field Mapping
Map the following Tosca fields to the model:
| Collection | Tosca Field | Model Field |
|---|---|---|
| Tosca Test Cases | Name | Action |
| UniqueId | Id |
Relationship Specification
Configure the following relationship mappings:
| Collection | Tosca Field | Model Field |
|---|---|---|
| Tosca Execution List Folders | Parent Folder | Parents |
Configure your Integrations
You can learn general details on configuring integrations here:
For this integration scenario, you will need to configure the following integrations:
- UiPath Requirements <> Tosca Requirements
- UiPath Test Sets <> Tosca Test Case Folders
- UiPath Test Cases <> Tosca Test Cases
- UiPath Test Executions <> Tosca Execution List Folders
- UiPath Defects <> Tosca Defects
Review the details in the table below to ensure that your integrations are configured correctly.
| Integration | Integration Type | Artifact Creation Flow | Test Step Flow | Container Mirror/Artifact Routing |
|---|---|---|---|---|
|
UiPath Requirements <> Tosca Requirements |
Work Item Synchronization | Two-way Creation | N/A | UiPath <> Tosca |
|
UiPath Test Sets <> Tosca Test Case Folders |
Container + Work Item Synchronization |
Two-way Creation | N/A | UiPath <> Tosca |
|
UiPath Test Cases <> Tosca Test Cases |
Work Item Synchronization | Two-way Creation |
One-way Flow Tosca accepts test steps |
UiPath <> Tosca |
|
UiPath Test Executions <> Tosca Execution List Folders |
Work Item Synchronization | Two-way Creation | N/A | UiPath <> Tosca |
|
UiPath Defects <> Tosca Defects |
Work Item Synchronization |
Two-way Creation |
N/A | UiPath <> Tosca |
Functional Limitations
| Category | Limitation | Applicable Repository Version |
|---|---|---|
| Configuration Requirement |
Test Steps Test Steps are supported for Test Cases, but you must select which direction you'd like test steps to flow during intial configuration. |
Any supported repository version:
|
| Configuration Requirement |
Test Cases Synchronization for the Test Case artifact can be bidirectional, but the Tosca Test Case Folder must be specified. |
Any supported repository version: |
| Third Party API Limitation |
Test Execution/Execution List Integration The Test Execution and Execution List integration is one-way from UiPath to Tosca due to a limitation in UiPath. |
Any supported repository version: |
| Feature Unsupported |
Test Step Results Test step results are not supported. |
Any supported repository version: |