- Automation Cloud and Test Cloud
- Automation Cloud Public Sector and Test Cloud Public Sector
- Automation Cloud Dedicated and Test Cloud Dedicated
- Integrations
November 2026
November 2026 release notes for Test Manager in Automation Cloud and Test Cloud.
November 5, 2026
Playwright test automation is generally available
Test Manager can execute test cases backed by Playwright automations, alongside Studio-authored (Robot) automations, without rewriting existing Playwright suites in Studio. Playwright is the first open-source test tool natively integrated in Test Manager. This capability is available in Test Manager only when delivered through Test Cloud.
Packaging and linking
- A new
uip tm packCommand Line Interface (CLI) command packages a Node.js Playwright (JavaScript/TypeScript) project into a UiPath automation package, publishable to Orchestrator like any other package. - Test Manager test cases are auto-created and auto-linked directly from your
test()blocks once Test Manager ingests a package that was built with a project key. - Playwright automations can be selected, updated, and unlinked through the existing Selecting automation and Unlinking automation flows — Playwright packages show a Source of Playwright alongside Studio's UiPath.
- New auto-managed
PW_system labels keep test cases searchable and filterable without touching your own labels.
Execution and reporting
- A test set's execution can be scoped to one or more Playwright projects through the new Playwright Projects dropdown when adding a package to a test set; each execution freezes its package, version, and project selection as a snapshot for reliable re-execution.
- Two new tabs on Playwright test case logs: Attempts, for per-attempt error context rendered inline, and Trace, for an embedded Playwright trace viewer with console logs, network calls, and downloadable attachments.
- Retry handling: a test that fails and then passes on retry is recorded as Passed, with the failed attempt(s) still visible in the Attempts tab and
wasFlaky: truerecorded in the per-test result attachment. - No change to licensing: Playwright executions consume the same platform capacity as any other serverless test execution, based on run time.
Execution constraints
- Chromium-only and serverless-only execution; Node.js Playwright projects only.
- One Orchestrator job per test set execution, with no multi-pod sharding.
- No enforced execution order: ordering follows
playwright.config.ts. - Mixing test cases from two different Playwright packages, or two versions of the same package, in one test set is blocked.
- Adding one data-driven test case variation to a test set runs all of its generated variations.
For more information, see Playwright test automation.
November 2, 2026
Run tests from a default project
Test Manager provides a default project on your tenant that stores the results of executions that do not specify a project. You can run tests from the UiPath Command Line Interface (CLI), uip, without first creating a project in Test Manager. Existing pipelines that do not pass a project keep working.
The default project has the following properties:
- Test Manager creates it automatically the first time it is requested through the API. Enabling Test Manager does not create it.
- Its name is
TMDefaultProjectand its project prefix isTMDP. - Tenant administrators can designate an existing project as the default with the new Default project for execution results setting on the General tab of the tenant level settings.
Running tests without a project is available in the UiPath CLI (uip) only. The .NET CLI and API runs still require a project. For more information, refer to Default project for execution results.
Custom fields of type URL
Create custom fields of type URL to link requirements, test cases, and test sets to the Jira issues, specifications, and internal documents they relate to. Each URL field stores a URL and an optional display text, shown as a clickable link that opens in a new browser tab.
This feature is available in Test Manager only when delivered via Test Cloud.
For more information, refer to the Custom fields section of the documentation.