Test cases with execution templates fail at runtime when published from Studio 2026.0.192

When publishing a test project containing test cases with execution templates from UiPath Studio 2026.0.192, running the tests from Test Manager fails with:

The .generated<TestCaseName>.xaml workflow cannot be found

The same project published using uipcli 25.10.14 or Studio 2025.10.10 works without issues.

Steps to reproduce:

Create a test project in UiPath Studio with at least one test case that uses an execution template

Publish the package from Studio 2026.0.192

Upload to Orchestrator and run from Test Manager

Observe the error

Expected behavior: Test executes successfully

Actual behavior: Runtime error — the .generated/ workflow file cannot be found

Environment:

Studio version: 2026.0.192
Working version: 2025.10.10 / uipcli 25.10.14

hey @Ted1 When publishing a test project containing test cases with execution templates from UiPath Studio 2026.0.192, running the tests from Test Manager fails with:

The .generated.xaml workflow cannot be found

The same project published using uipcli 25.10.14 or Studio 2025.10.10 works without issues.
Steps to reproduce:
Create a test project in UiPath Studio with at least one test case that uses an execution template

Publish the package from Studio 2026.0.192
Upload to Orchestrator and run from Test Manager
Observe the error
Expected behavior: Test executes successfully
Actual behavior: Runtime error — the .generated/ workflow file cannot be found
Environment:
Studio version: 2026.0.192
Working version: 2025.10.10 / uipcli 25.10.14

This issue is caused by a packaging bug in UiPath Studio 2026.0.192 , where .generated workflow files (created for test cases using execution templates) are not included in the published package. As a result, Test Manager cannot find the required .generated\<TestCaseName>.xaml file at runtime.

Workaround:
Publish the test project using a stable version such as Studio 2025.10.10 or uipcli 25.10.14 , where the .generated folder is correctly included in the package. The published package will then execute successfully from Test Manager.

Alternatively, avoid using execution templates temporarily until the issue is fixed in newer versions.

The generated template are actually included in the package. I downloaded the package from Orchestrator and its there. I think its a mapping issue.

Hi @Ted1 , I’ve raised this with our engineering team to further investigate this.

I dont know if there was some changes or something else, but after the reason studio update the test cases with execution template now works!