# Test Cases

> :::important
The Orchestrator Testing module was deprecated on January 1, 2026. For more information consult the [Deprecation timeline](https://docs.uipath.com/overview/other/latest/overview/deprecation-timeline#orchestrator) section and the [FAQ](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/faq---deprecating-the-testing-module) section.
:::

## Overview

:::important
The Orchestrator Testing module was deprecated on January 1, 2026. For more information consult the [Deprecation timeline](https://docs.uipath.com/overview/other/latest/overview/deprecation-timeline#orchestrator) section and the [FAQ](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/faq---deprecating-the-testing-module) section.
:::

In this topic, you can learn how to manage your test cases across all the projects and application versions. The test cases are part of test sets that are up for execution. For more information, check the [Test Sets](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/test-sets#test-sets) page.

## Conditions

* The test cases are created automatically when you publish a test package through Studio. For more information, see [Introduction](https://docs.uipath.com/studio/standalone/latest/user-guide/introduction-studiopro).
* If an existing package is revised followed by an updated version being published, the test cases for the new version are automatically created. The new test cases show up alongside existing ones for the previous version. However, if the changes to the package only apply to the patch version, then the existing test cases are updated to reflect these changes, instead of creating new ones.
* When you publish a new test case version, the correspondent package is automatically updated to the latest version.
* If an existing project is cloned to represent a new application version (e.g. from `v1.1.1` to `v.1.2.0`), you must manually publish this package and create a new process.
  :::important
  * To create and run test automation jobs, you must
  have the following roles assigned: [Automation User](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/default-roles#automation-user) and [Robot](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/default-roles#robot-role).
  * You must first [deploy a process](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/managing-processes#managing-processes) from the published
  test case package before you can create and execute a test set.
  :::

## Create Test Set

You can group together multiple test cases into a test set.

1. Log in to Orchestrator.
2. Open your folder.
3. Navigate to **Testing** > **Test Cases**.
4. Use the checkboxes to select individual test cases. Alternatively, you can choose **Select all** in the column header. You can modify the test case selection later in the test set configuration step.
5. Select **Add test set**.
6. Enter a **Name** and an optional **Description** for your test set and then click **Create** to continue.
7. Configure the execution target. You can select the user that is assigned to that specific folder. The default is set to **Any User**.
8. Select your Studio projects.
9. (Optional) You can edit the project version and toggle to **Include Prerelease** versions.

Figure 1. Editing a project version

   ![Screenshot of the Edit project version page](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-edit-project-version-page-226767-59e9c11b-921219b3.webp)

10. Define custom **Arguments** for your test cases to override default values at the test set level.

Through the arguments, you can parameterize the test cases at runtime.

:::note
To define arguments, you need to have published a package with arguments.
:::

11. Select **Next** to continue.
12. Modify test case selection if needed.
13. Select **Save**. Your test set is created and available on the **Test Sets** page.
    :::tip
    * [Create test set on the Test
    Sets page](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/test-sets#test-sets)
    * [Execute individual test
    set](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/test-sets#test-sets)
    * [Add test
    schedule](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/test-schedules#test-schedules)
    :::

## Execute Test Case

:::important
For any new tenant, test management capabilities have been moved to Test Manager. As a result, you cannot execute test cases anymore directly from Orchestrator on these tenants, except through [Orchestrator APIs for Test automation](https://docs.uipath.com/orchestrator/automation-cloud/llatest/api-Guide/permissions-per-endpoint#test-automation), or using [CI/CD integrations](https://docs.uipath.com/cicd-integrations/standalone/2025.10/user-guide/about-cicd-pipelines). The Orchestrator Testing module was deprecated on January 1, 2026. For more information consult the [Deprecation timeline](https://docs.uipath.com/overview/other/latest/overview/deprecation-timeline#orchestrator) section and the [FAQ](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/faq---deprecating-the-testing-module) section.
:::

You can execute individual test cases on the **Test Cases** page.

1. Log in to Orchestrator.
2. Open your folder.
3. Navigate to **Testing** > **Test Cases**.
4. Select a test case and click **Execute**.
5. Configure the execution target:
   * **Runtime type**: Select a runtime type out of the ones available for your tenant.
   * **Account**: Select the account from the dropdown list that is assigned to that specific folder. The default is set to **Any User/Robot account**.
   * **Machine**: Select the machine resource from the dropdown list.
6. Click **Execute** to confirm.

## Delete Test Case

1. Open your folder in Orchestrator.
2. Navigate to **Testing** > **Test Cases**.
3. Select a test case and click **Delete**.
4. Click **Ok** to confirm.