# Analyze test results
> To view test executions, open **Execution** in Test Manager. The execution of each test set is listed as a test execution entry. To understand how the test executions work behind the scenes, see [Execution](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/test-results).
To view test executions, open **Execution** in Test Manager. The execution of each test set is listed as a test execution entry. To understand how the test executions work behind the scenes, see [Execution](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/test-results).
By analyzing your test execution, you can take the following actions:
* Find test results that have been executed manually or automatically through Orchestrator.
* Check the progress on running test executions.
* Open the test set that has been executed.
* Examine logs and attachments.
* Create defects in your defect management system directly from Test Manager, if you have an Application Lifecycle Management tool integration. For more information, see [ALM Tool Integration](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/about-alm-tool-connectors#alm-tool-integration).
By default, the test executions are sorted based on the date on which the execution was finished. Currently running and pending executions are placed at the top.
You can identify the status through the color codes assigned to each test execution, as follows.:
* **Green**: Test cases that passed.
* **Red**: Test cases that failed.
* **Grey**: Test cases without a definitive results, such as test cases that have not been executed yet but are part of a test set that is currently being executed.
## Results from automated tests
The results from automated test executions are imported from Orchestrator automatically. To have your automated tests imported to Test Manager, you need to meet the following conditions:
* The automated test needs to be associated with a test case from Test Manager in any project of the same tenant. For more information, see [Automated Tests](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/executing-tests) and [Selecting automation](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/selecting-automation).
:::note
If a Test Execution from Orchestrator holds results for test cases from several projects in Test Manager, the test execution is split in Test Manager. The results appear in the projects where the test cases are.
:::
### Viewing results based on user license
Your user license determines the automated test execution results you can view:
* Pro or Plus license: You can only view and interact with results or test case logs executed on Testing robots with `TestAutomation` runtime type. You cannot interact with results or test case logs executed by App Testing robots with the `AppTest` runtime type, as they are disabled.
* App Tester or App Test Developer license: You can view and interact with results or test case logs executed by both Testing and App Testing robots, including both the `TestAutomation` and `AppTest` runtime types.
For more information on licensing, visit [Unified Pricing: Licensing Test Manager](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/licensing-test-manager#unified-pricing%3A-licensing-test-manager).
### Viewing live stream of test execution
If you enabled live streaming for a test execution or test set, you can access the recording after the execution completes.
To view the live stream recording:
1. Go to the **Results** section of the test execution.
2. In the **Video** column, select **Live**.
This tab displays the recording of the test execution as captured during live streaming.
## Overriding test results
Overriding the results of a test case can help in scenarios where the current test result does not accurately reflect the actual behavior of the application and re-execution is not an effective solution. You can override the test results of a test case and then you can clear the operation, if needed.
1. Navigate to **Execution** and open a test result.
2. From the **Results** tab open a test case log.
3. In the **Assertions** tab, select **Tasks** > **Override result**.
4. In the **Override test result** window configure the following fields:
1. **Change result to** - select whether you want to override the result with the opposite status (**Passed**/**Failed**) or set the result to **None**.
2. **Comment** - Type the reason why you override the result.
5. Select **Confirm**. The test results that you overrode have the following icon next to the test result status: . Select the icon and you can view the override details.
Figure 1. The "Test result overridden successfully" message
6. Optionally, if you want to clear the override operation, select the  next to the result status of a test case log.
1. In the **Override details** window, select **Clear override**.
Figure 2. The **Override details** menu
7. Optionally, if you want to edit the override operation, select the  next to the result status of a test case log.
1. Perform changes, and click **Confirm**.
## Navigation and search
To quickly find your test results, use the search function and the filters. Navigate within the page using and configuring the paginator. Alternatively, you can use the breadcrumb to navigate between the pages.
1. **Filters** - You can use the filters to narrow your search. For example, you can search for test results by the following criteria:
1. Labels
2. Execution Type
3. Execution Finished
4. StatusThe filters are automatically saved and kept active until you clear them.
2. **Search** - Use the search bar to find test results by their key, execution type or status (requires full search term match). You can use the search bar at the top of the page to look for test results.
## Working with test execution results
To view detailed test results, go to **Execution**.
In the **Results** tab, select **View By** and choose your preferred view for test results. You can select one of the following views:
* **Test Set**: Test results are grouped by Test Execution (Test Set).
* **Test Case**: For cross-execution analysis when filtering the results based on criteria excluding test execution attributes.
Select an entry to open the detailed view. A typical test execution detailed view shows information on when the executions started, duration, and [execution logs](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/analyzing-test-results#execution-log).
You can access the execution log of a test case from the **Test Case** view by selecting the relevant result chip. If the postcondition of a test case wasn't met during a manual execution, the test case log displays an exception with an **Info** icon. The exception message reads: **Exception during execution. View logs for details**. Selecting this message takes you to the **Execution details** tab of the corresponding test case log.
You can use the **Reporting Date** filter to set a unified date across all test results from the test execution. This is useful when you run tests overnight, where some test cases are executed before and after midnight, preventing results from splitting onto separate dates.
In the **Results** tab you can examine all the executed test cases within the test set, and take action for each, as necessary. For more information, see the **Execution log** section.
You can also open the executed test set by right-clicking an entry in the **Test Sets** page and selecting **Open Test Set**, or directly within the test execution.
## Execution log
As part of test reporting, execution logs hold information such as execution details (e.g., data variation and screenshots), failed and passed assertions, and a detailed log of execution events. Robot and Assertion logs are available in real-time as soon as the test case starts executing. You can also view the machine on which the test runs and the robot used to run the execution.
To open a test case log, go to **Executions**, open a test execution and then select a test case **Key**, or result.
Figure 3. Overview of the execution details of a test case log
In the following table, you can view the type of information that is collected during test case execution.
Test execution reporting
Description
Assertions
View failed or passed assertions (e.g., Verify expression activity ), and associated screenshots if any were taken during test case execution. To make sure that Orchestrator takes screenshots during executions, visit the following resources:
Default roles in Orchestrator - to check if the default roles have the Test Case Execution Artifacts permission assigned. In case the default roles don't have this permission, then you can create a custom role with this permission.
Managing roles in Orchestrator - to learn how to create, edit, or import a role in Orchestrator.
Logs
View INFO level logs as part of the RobotLogs , with information about processes, execution robot, and event logs, including failures. Select the icon to go to the Logs tab of the selected test case, for a detailed description of the failure.
Execution details
View argument details such as input and output values, as well as execution and robot details (e.g., project, machine, robot). This section also indicates whether the postcondition was met by the test case or not.
Affected requirements
View the requirements that are assigned to the test case that has been executed. You can use this tab to go directly to the affected requirement.
Attachments
You can view the following:
Attachments uploaded using the Attach Document activity.
Attachments of a test case result, that is linked from Orchestrator.
You can check test logs (Assertions, Robots) as soon as the execution status changes to **Running**.
1. Go to **Execution**.
2. Select an execution.
3. Select the **Results** tab. Check if the execution status is **Running**. Select the test case key.
4. Check the following tabs which get populated every ten seconds, as the execution progresses: **Assertions**, **Logs**, and **Healing Logs**. Note that **Healing Logs** are available only for Test Cloud users.
### Execution details
The **Execution details** tab of a test case log offers information about the preconditions ad postconditions of a test case.
If the postcondition was not met during the test execution, then the tab displays the **Condition not met** warning, that you can investigate.
Figure 4. The **Condition not met** warning
### Downloading execution logs
From the **Execution** section of your project, you can export your executions either to XLSX or PDF. Downloading execution logs allows you to further analyse test results.
#### Downloading execution logs for all test executions
To download logs for all your test executions, follow these steps:
1. Go to the **Execution** section of your project.
2. Select **Export to Excel**.
This action exports all test executions in a `.xlsx` file.
#### Downloading execution logs for an execution
When you download execution logs for an execution, you obtain a PDF or XLSX version of your test results.
To download test case logs for a specific test execution (all test cases within an execution), follow these steps:
1. Go to **Execution** section of your project.
2. Select a test execution.
3. Select **Export**, and then choose one of the following outputs:
* **Download Excel** – Export logs in a `.xlsx` file.
* **Download PDF** – Export logs in a `.pdf` file.
To download test case logs individually, follow these steps:
1. Go to **Execution**.
2. Select a test execution.
3. In the **Results** tab, identify the test case log you want to download.
4. Go to the end of the row, select the vertical three-dot menu, and, from the context menu, select **Export as PDF**.
5. Alternatively, to download several, individual test case logs, select their check boxes, and from the upper right-hand corner of the results grid, select **Export as PDF**. The test case logs are exported as individual files in a .ZIP archive.
Visit [Export data](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/export-data#export-data) to check more details about exporting logs to XLSX or PDF files.
## Viewing activity coverage
:::note
Activity coverage is available only for automated test executions.
:::
**Prerequisites**: Enable activity coverage for the desired test sets either in Orchestrator or Test Manager.
1. Open the test set, select **More Options**  and then **Execute Automated**.
2. Go to **Execution** and open the test set you executed.
3. Go to the **Activity Coverage** tab and investigate the information on the activities that were covered during the test execution.
Figure 5. Overview of an example activity coverage
## Create defects from results
You can create defect reports including the execution log to your external defect management system, if you already have it integrated with Test Manager. For more information, see [ALM Tool Integration](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/about-alm-tool-connectors#alm-tool-integration).
To create a defect out of an execution log, you need to open a test case log, click **Tasks**, and then select **Create Defect**. After the defect has been created, a link is available in the execution log, so you can access the integrated external tool.
## Related articles
* [Bulk Operations](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/bulk-operations#bulk-operations)
* [Export Data](https://docs.uipath.com/test-manager/automation-cloud/latest/user-guide/export-data#export-data)