The execution outcome in ADO is showing “In Progress” but all these executions are already “Passed” in Test Manager
Issue Description
When synchronizing Test Execution (UiPath Test Manager) and Test Run data (ADO Azure DevOps) using Planview, the synchronization process may get stuck in the "In Progress" state. This issue prevents test execution statuses from updating correctly, leading to inconsistencies between ADO and UiPath Test Manager.
Root Cause
The synchronization issue occurs due to incorrect mapping between the statuses in ADO and UiPath Test Manager.
Resolution
To resolve this issue, follow these steps to map statuses correctly and ensure a smooth synchronization process:
Step 1: Verify ADO Status Fields
Confirm that the UiPath Test Manager Test Execution Status and ADO Test Run Status fields are correctly set up as Single Select fields with the following values:
UiPath Test Execution Status:
-
- Finished
- Running
- Cancelled
- Pending
- Cancelling
ADO Test Run Status:
-
- Needs Investigation
- Not Started
- Completed
- In Progress
- Unspecified
- Aborted
- Waiting
Step 2: Ensure a Test Run Exists in ADO
Before attempting to synchronize, make sure that at least one Test Run has been created in ADO. This is essential for UiPath Test Manager Connect to retrieve the correct Test Execution schema from ADO. If this step is skipped, the UiPath Test Manager Connect collection may return errors.
Step 3: Verify the collection from ADO
ADO test run collection should look like the one below:
- Map the Uipath Test Execution Status to the ADO Test Run Status.
- Set the "Transform Field" (Collection → Model) to None to ensure that the correct status values are passed without transformation.
- Ensure that the final integration mapping aligns with the expected status values in both systems.
Step 4: Verify the collection from UiPath Test Manager
Step 5: Validate Synchronization
- Run the integration and check that Test Run statuses in ADO match the corresponding Test Execution statuses in UiPath Test Manager.
- Verify that the synchronization no longer gets stuck in the "In Progress" state.
- Ensure that both the UiPath collection and ADO test run collection reflect the expected structure.
The final integration should be properly configured to sync statuses between the two systems.
Note:
If Test Results are not synced and are required for the integration, be aware that this is due to a known product limitation. Check this page for more details and updates: Planview Hub - Functional Limitations for Azure DevOps Server.
Currently, the limitation states: Test Results cannot be added to a Test Run in the “Completed” state.
Therefore, mapping to the “Completed” state is not recommended if there is a plan to synchronize Test Results.





