# Test Executions > :::important Test management capabilities have been moved to Test Manager. As a result, for any new tenant, you cannot execute test cases directly from the Orchestrator user interface anymore, except through [Orchestrator APIs for Test automation](https://docs.uipath.com/orchestrator/automation-suite/l2.2510/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). To execute test cases, use Test Manager instead. ::: ## Overview :::important Test management capabilities have been moved to Test Manager. As a result, for any new tenant, you cannot execute test cases directly from the Orchestrator user interface anymore, except through [Orchestrator APIs for Test automation](https://docs.uipath.com/orchestrator/automation-suite/l2.2510/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). To execute test cases, use Test Manager instead. ::: In this topic, you can learn how to manage your test executions. The test executions serve as an immutable record of the execution of any respective test set, at a specific point in time. By comparison, the test set is always subject to change, as it can target a different application version or its test case selection can be modified. **Prerequisites**: To perform test executions, you need to have the [Robot role](https://docs.uipath.com/orchestrator/automation-suite/2.2510/user-guide/default-roles#robot-role) assigned. ### Executing test cases that contain Integration Service connections For test cases and projects that contain test cases created using a specific Integration Service connection, you cannot assign a specific connection at runtime, other than the one used during the design phase in Studio, For example, if you create a test case containing an Integration Service connection, then publish it to Orchestrator and execute it independently, there will be no option available to assign a specific connection at runtime. If you publish a Studio project containing test cases using Integration Service connections to Orchestrator as a Process, the option to configure the connection at runtime will be available under the **Package Requirements** of the process. :::note When configuring the connection in the **Package Requirements** of the test cases will continue to use the design-time connection previously selected in Studio. ::: ## Re-execute Test Set :::important For any new tenant, you can re-execute test sets only using [Orchestrator APIs for Test automation](https://docs.uipath.com/orchestrator/automation-suite/l2.2510/api-Guide/permissions-per-endpoint#test-automation). ::: You can re-execute test sets after a previous run. The new test case result will override the previous one shown on the **Test Executions** page. Be aware that you cannot re-execute test cases from a Test Set with enabled coverage calculation. 1. Log in to Orchestrator. 2. Open your folder. 3. Navigate to **Testing** > **Test Executions**. 4. Select a test run and go to **More actions** > **Details**. 5. Select a test case and go to **More actions** > **Re-execute**. 6. Configure the execution target: * **User**: Select the user from the dropdown list that is assigned to that specific folder. The default is set to **Any User**. * **Machine**: Select the machine resource from the dropdown list. 7. (Optional) Define custom Arguments for your test cases to override default values at the test set level. To define arguments, you need to have published a package with arguments. 8. Click **Execute** to confirm. ### Known limitation The results from re-executing a test set in Orchestrator are not synced to Test Manager. We recommend you to execute and re-execute tests directly from Test Manager. ## Test Execution Coverage :::important For any new tenant, test execution coverage is not available. You can view the activity coverage of your tests in Test Manager. For more information, visit [Viewing activity coverage](https://docs.uipath.com/test-manager/automation-suite/2.2510/user-guide/analyzing-test-results#viewing-activity-coverage). ::: You can view information on the activities that have been covered during a test execution. This option is also available in Studio, as [Activity Coverage](https://docs.uipath.com/studio/docs/rpa-testing-activity-coverage). :::important Activity coverage calculator is available when you select this option for existing or new test sets. For more information, see [Create test set](https://docs.uipath.com/orchestrator/automation-suite/2.2510/user-guide/test-sets#test-sets). ::: 1. Open your folder in Orchestrator. 2. Navigate to **Testing** > **Test Executions**. 3. Select a test run and go to **More actions** > **Details**. 4. Go to the **Coverage** tab to view coverage details. The coverage files are uploaded to the **Attachments** tab. Figure 1. Coverage tab ![Screenshot of the Coverage tab](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-docs-image-227087-e621a819.webp) ## Analyze Test Executions You can analyze test executions to understand what happened in instances where the execution failed or got stuck. :::note You can view screenshots of failed test executions by navigating to **Automations** > **Job** > **Job Details**. To benefit from this feature, you need to enable execution media at the application level. For more information, see [Execution Media Permissions](https://docs.uipath.com/orchestrator/automation-suite/2.2510/user-guide/about-recording#recording). ::: Figure 2. Execution details ![Screenshot of the Execution details window](https://dev-assets.cms.uipath.com/assets/images/orchestrator/orchestrator-screenshot-of-the-execution-details-window-233208-e3867d42.webp) You can choose from the following actions to examine your test runs. Actions Description Procedure Execution details View Robot details, including execution attachments, data variation and screenshots. Make sure that you have Execution Media Permissions . Open your folder in Orchestrator. Navigate to Testing > Test Executions . Select a test run and go to More Actions > Details Click Details to view the execution details. View assertions View failed or passed assertions. Open your folder in Orchestrator. Navigate to Testing > Test Executions . Select a test run and go to More actions > Details . Select a test case and go to More actions > View assertions . View logs View and export a detailed log of execution events. Open your folder in Orchestrator. Navigate to Testing > Test Executions . Select a test run and go to More actions > Details . Select a test case and go to More details > View logs . Click Export to get the test execution details in a CSV format. ## Test Executions API To query for item related activities, you can use the Background Tasks, internally available through API. For more information on Orchestrator Permissions, see. For more information on test automation API, see [Test Automation API Permissions](https://docs.uipath.com/orchestrator/standalone/2022.10/api-guide/permissions-per-endpoint#test-automation).