June 2026

June 15, 2026

What's New

Project configuration in export and import operations

Test Manager supports exporting and importing Project Configuration as part of TMH files, making it easier to move project settings together with project data or transfer configuration independently.

When you select Project Configuration during export, the TMH file can include:

• Custom field definitions
• Project user authorizations and roles
• Default reporting time zone
• Default automation context folder
• Governance settings

During import, users can choose whether to apply the configuration contained in the TMH file or not.

This feature supports compatibility across Test Manager versions.

For more information about importing TMH files, refer to the Import projects section of the documentation. For more information about exporting TMH files, refer to the Export projects section of the documentation.

Sort groups in custom structured views

You can sort groups ascending or descending when working with custom structured views.

Note:

The Sort groups feature is available in Test Manager only when delivered via Test Cloud.

For more information about custom structured views, refer to the requirements documentation, the test cases documentation, and the test sets documentation.

Romanian language support for system prompts

Romanian is a supported language for Autopilot.

For more information about Autopilot, refer to the About Autopilot section of the documentation.

Retry operations and error handling in Performance Testing

The accuracy of Test Automation reporting has been improved by differentiating the expected retry behavior from genuine execution failures. Retries that occur during UI control interactions (commonly used to handle dynamic application timing and improve automation resilience) are no longer classified as errors when the action ultimately succeeds.

Benefits of this change:

• Error charts now reflect only true failures that impact execution outcomes
• Retry attempts no longer artificially inflate error counts
• Successful workflows that complete after retries are correctly reported as successful executions
• Provides a more reliable view of test stability and application quality

Troubleshooting and visibility:

Retry attempts remain visible in execution logs and can be differentiated from actual blocking errors. This gives teams clearer insights into automation behavior, reduces false-positive error reporting, and helps focus investigation efforts on issues that genuinely affect test results.

For more information on Performance Testing results, refer to the Analyzing performance results section of the documentation.

Workflow analyzer in Performance Testing

Performance Testing now includes a Workflow Analyzer that automatically scans test automation projects during dry runs. The analyzer identifies:

• Selectors and interaction modes not compatible with performance testing
• Workflow patterns that may not scale
• Issues in the full workflow invocation chain (not just the entry test case)

How it works:

The analysis runs as a lightweight pre-flight validation step and surfaces warnings or errors early in the testing process. This fail-fast approach helps teams detect unsupported automation patterns before virtual users are launched, reducing troubleshooting time and preventing misleading test results.

Benefits:

Teams can improve test reliability, accelerate performance test preparation, and gain greater confidence that their test cases are ready for large-scale execution.

For more information on performing a dry run as part of Performance Testing, refer to the Executing performance scenarios section of the documentation.

Live streaming in Performance Testing

Live Streaming has been introduced for Performance Testing, providing real-time visibility into test execution during dry runs. Users can open a live stream directly from an active dry run and observe test activity as it happens, helping identify issues earlier and reducing troubleshooting time.

Availability and status:

Live streaming is available only during active dry runs and can be enabled or disabled as needed. Clear status indicators inform users when a live stream is available, when it has not been enabled, or when a dry run has ended and streaming is no longer possible.

Benefits:

By providing immediate insight into test behavior, Live Streaming helps Performance Testing teams:

• Validate configurations
• Investigate automation issues faster
• Gain confidence before launching full-scale executions

This improves troubleshooting efficiency, shortens feedback cycles, and reduces the risk of issues progressing into production performance tests.

For more information on performing a dry run as part of Performance Testing, refer to the Executing performance scenarios section of the documentation.

June 8, 2026

What's New

Autopilot Chat Generally Available (GA)

Autopilot Chat is a context-aware and action-enabled agent which is generally available in Test Manager. Autopilot Chat is available in Test Manager only when delivered through Test Cloud.

• Autopilot Chat brings an intelligent, conversational assistant in Test Manager, designed to enhance how testers interact with and manage their testing assets.
• Instead of navigating menus and filters, users can ask questions, perform searches, generate assets, and trigger actions in natural language. The chat maintains conversational context when using tools, making interactions more natural and fluid.

Autopilot Chat connects with Test Manager's built-in Autopilot tools and extends further through MCP server integration, allowing it to execute commands, evaluate requirements, generate test cases, and even run external automation processes and agents.

Autopilot Chat is deployed in the following regions: EU, US, JA, CA, AUS, SI, UK, IN. For more information, refer to the Global cloud regions section of the documentation.

The LLMs which support Autopilot Chat are deployed in the following regions: EU, US, JP. For all the other available regions, the LLMs are re-routed. For more information, refer to the AI features and model routing section of the documentation.

• For more information about Autopilot Chat, refer to the Autopilot Chat section of the documentation in Test Manager and the Autopilot generic documentation.
• For additional information and recorded tutorials, subscribe to the complementary information maintained on the UiPath Insider Portal where you can also leave feedback.

MCP Server capabilities

MCP Server capabilities are integrated with Test Manager.

What is MCP?

MCP stands for Model Context Protocol — a modern standard that allows AI systems (like Autopilot Chat) to securely connect to external data sources, tools, and automation workflows. MCP works as a bridge between your AI assistant and the systems or APIs it needs to interact with. An MCP server hosts a set of tools (or "capabilities") that the AI agent can call when it detects relevant intent in your chat prompt.

Supported MCP servers:

In addition to the built-in Test Manager MCP server, only the MCP servers created in Orchestrator are supported. To learn more, refer to:

• Orchestrator - About MCP Servers
• Orchestrator - Managing MCP Servers

To configure MCP servers, refer to the Autopilot - User interface topic. MCP Server is available as part of Autopilot Chat in Test Manager only when delivered through Test Cloud.

Unified outbound IP ranges — transition begins

Test Manager outbound IP ranges are being unified. The new unified outbound IP ranges apply per regions (for example, United States, Europe, etc.) and are the same for all UiPath services within a region. This change affects the outbound IP ranges used for SAP integrations and connector communications.

For the full list of affected services, refer to the June 8, 2026 Automation Cloud release notes.

The current Test Manager outbound IP ranges will remain active until September 16, 2026. Starting September 16, they will be progressively phased out as the unified IP ranges take effect.

What you need to do:

1. Add the new unified IP ranges to your firewall configuration now. Find the full list of unified outbound IP ranges by region on the Configuring the firewall for Automation Cloud page.
2. Until September 16, 2026: Keep both the current Test Manager outbound IP ranges (on the Legacy - Configuring the firewall for Automation Cloud page) and the new unified IP ranges allowlisted simultaneously.
3. After September 16, 2026: Continue allowlisting both sets of IP ranges until a subsequent release note confirms the legacy IP ranges can be safely removed.

June 2, 2026

South Korea region support for Test Manager

As part of our ongoing cloud expansion, we're bringing complete data sovereignty to the South Korea region for Test Manager. This ensures your data is securely stored and replicated across multiple availability zones within South Korea, offering full control and compliance confidence. For more information, refer to the Global cloud regions page.