# Test Cases > Create and run application test cases in Studio using VB or C# for data verification and CI/CD pipeline integration scenarios. ## Creating application test cases Application testing in Studio works in either VB or C#. You can create individual automation projects for scenarios like data verification or integration with your CI/CD pipeline. Design your workflow in Studio. You can perform automated application testing in VB or C#. ### Conditions * Perform application testing through regular test cases and [data-driven test cases](https://docs.uipath.com/studio/standalone/2026.10/user-guide/data-driven-testing). * **Test Automation** projects can have multiple entry points if they contain several test cases with linear execution, as the activities are organized sequentially. * Workflow execution is performed per test case unless other `XAML` files are invoked. * You can convert workflows to test cases, import from other projects or create new ones. ### Dependencies * To perform application testing, you need to work with a **Test Automation** project. * To perform verifications, generate random test data, and manage your existing test data, you need to install the [Testing Activities Package](https://docs.uipath.com/activities/other/latest/workflow/about-the-testing-activities-pack). ### Steps 1. Open your project of type **Test Automation**. 2. In the Studio design ribbon, select the **New** dropdown list. 3. Select **Test Case** or **Coded Test Case**. 4. In the **New Test Case** menu, configure the test case that you want to create: 1. Give the test case a name. 2. Optionally, select a test case template based on which you want to create your test case. For information on test case templates, visit [Test Case Templates](https://docs.uipath.com/studio/standalone/2026.10/user-guide/test-automation-test-case-templates#test-case-templates) 3. Optionally, choose an execution template. For information on execution templates, visit [Execution Templates](https://docs.uipath.com/studio/standalone/2026.10/user-guide/execution-templates#execution-templates). Figure 1. The New Test Case menu ![The New Test Case menu](https://dev-assets.cms.uipath.com/assets/images/studio/studio-the-new-test-case-menu-570530-34d0ec97.webp) 5. Select **Next** to navigate to the **Test Data** section, where you can configure specific test data for this test case. 6. Select **Create** to finish the test case creation. #### Result The application test case is created and added to the project as a new file. ## Creating RPA test cases RPA testing in Studio works in either VB or C#. You can create individual automation projects for scenarios like data verification or integration with your CI/CD pipeline. Design your workflow in Studio. You can perform automated RPA testing in VB or C#. ### Conditions * Perform RPA testing through regular test cases and [data-driven test cases](https://docs.uipath.com/studio/standalone/2026.10/user-guide/data-driven-testing). * Workflow execution is performed per test case unless other `XAML` files are invoked. * You can convert workflows to test cases, import from other projects or create new ones. ### Dependencies * To perform RPA testing, you need to work with a **Process** project type. * To perform verifications, generate random test data, and manage your existing test data, you need to install the [Testing Activities Package](https://docs.uipath.com/activities/other/latest/workflow/about-the-testing-activities-pack). ### Steps 1. Open your project of type **Process**. 2. You can create a test case by invoking a workflow from an existing project, either from the **New** file menu, or from the **Project** panel: * In the **New** file menu, select **Test Case**. * In the **Project** panel, right-click the workflow and choose **Create Test Case**. ![Project panel context menu showing the Create Test Case option for a workflow](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-167289-9aa5c045.webp) 3. (Optional) Select **Mock workflow under test** when you create your test case if you want to make a copy of your workflow where you can mock specific activities. If you have an existing mock file that you want to use, you can select it from the **Mock** dropdown list. For more information, see [Mock Testing](https://docs.uipath.com/studio/standalone/2026.10/user-guide/mock-testing). ![New test case dialog with Mock workflow under test option and Mock dropdown list](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-168045-9fdb0c88.webp) 4. (Optional) Select a **Template** from the dropdown list if you have created one previously. For more information, see [Test Case Templates](https://docs.uipath.com/studio/standalone/2026.10/user-guide/test-automation-test-case-templates#test-case-templates). 5. (Optional) Add the test case to an **Execution Template**. You need to have created an execution template first. For more information, see [Create execution template](https://docs.uipath.com/studio/standalone/2026.10/user-guide/execution-templates#execution-templates). 6. Select **Next** if you want to [add test data](https://docs.uipath.com/studio/standalone/2026.10/user-guide/data-driven-testing). 7. Select **Create** to confirm the changes. A test case `XAML` file is created invoking the workflow with the following containers: **Given**, **When**, and **Then**. The file is invoked inside the **Invoke Workflow File** activity, part of the **When** container. ![Test case XAML with Given, When, and Then containers and Invoke Workflow File activity](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-168773-b76be4f9.webp) 8. Arguments from the workflow are automatically imported. To view or add more arguments, select **Import Arguments** in the **Invoke Workflow File** activity. #### Result The test case is created as a XAML file and added to the project. Workflow arguments are automatically imported. ### Related articles * [Add test data](https://docs.uipath.com/studio/standalone/2026.10/user-guide/data-driven-testing) * [Mock testing](https://docs.uipath.com/studio/standalone/2026.10/user-guide/mock-testing) * [Link test cases to Test Manager](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/managing-test-cases) ## Publishing test cases If you have test cases within your project, then you can choose to either publish the entire project (**Publish**) or only the test cases (**Publish test cases**). If you are working with a **Test Automation** project, you can only publish test cases to Orchestrator. To publish the test cases that you create in Studio, you must set the test cases as publishable, because both test cases and data-driven test cases are created as drafts by default. To publish the test cases within all types of Studio projects, perform the following steps: 1. Open the context menu for a test case and select **Set as Publishable**, to allow the test case to publish to Orchestrator. ![Project panel context menu with Set as Publishable option selected for a test case](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-171720-a79e0414.webp) The `xaml` or `cs` icon will turn blue as an indication that the test case is ready to be published and packaged in a `nupkg` file. To revert back to your workflow draft, right-click the workflow and select **Ignore from Publishing**. 2. Publish the project: * If you are in a **Test Automation** project, select **Publish** in the Studio **Design** tab ribbon, expand the **Publish** option, and select **Publish**. * If you are in a **Process** or **Library** project, select **Publish test cases** from the Studio **Design** tab ribbon, expand the **Publish** option, and select **Publish test cases**. 3. Configure the **Package properties**, **Publish Options**, and the **Certificate signing** settings for the publishing action, then select **Publish** to publish your test cases to Orchestrator. :::important You can publish test cases to Orchestrator, Robot defaults, or a custom path. To publish to Orchestrator, ensure your [Robot or Assistant is connected](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/connecting-robots-to-orchestrator). Publishing to Orchestrator is required to [execute tests through Test Manager](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/executing-tests). Publish the package to the Orchestrator Tenant Process Feed and [link it to a Test Manager test case](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/selecting-automation). Publishing to other folders may cause execution errors. ::: ### Result The test cases are published to Orchestrator and available for execution. ## Converting workflow to test case To convert workflows into test cases, right-click the workflow in the **Project** panel and select **Convert to Test Case**: ![Project panel context menu showing Convert to Test Case option for a workflow](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-167661-4c21762b.webp) Alternatively, to convert a test case back into a workflow, right-click a test case and select **Convert to Workflow**. ## Importing test cases If you already created workflows or test cases, you can import them into your current project by right-clicking the project node, and selecting **Import Test Cases**. The imported `XAML` files are added to your project as draft test cases. ![Project panel context menu with Import Test Cases option for adding existing workflows](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-167681-2f786948.webp) ## Importing services Similarly to importing data collections into [API Test Automation](https://docs.uipath.com/studio/standalone/2026.10/user-guide/api-test-automation#api-test-automation) libraries, you can import such collections into your application testing projects using the **New Service** wizard. :::note This is available only for libraries and **Test Automation** projects. Additionally, only App Test Developer users can create and publish **Test Automation** projects. :::