---
title: "Test Runs Report"
canonical: "https://docs.getxray.app/space/XRAY/301407335/Test%20Runs%20Report"
format: markdown
---
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> > Macro (toc)
# Introduction
The Test Runs report shows a list of Test Runs with detailed information for each one, including related Test, Test Execution, and Test Plan entities, execution dates, and Linked [Defects](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301469601).
> ⚠️ To use this report, your project must have the Test Execution or Sub-Test Execution Issue Types in the Issue Type scheme.
This report enables you to see which tests were or are going to be executed, along with the corresponding result and key metrics.
Possible usage scenarios:
- Seeing all the runs of a given Test Execution.
- Checking all the runs of all Test Executions related to a Test Plan.
- Verifying the number of opened/closed linked defects in the context of a given run.
- Seeing the elapsed time since the execution started.
- Checking the executions performed by or assigned to a given user.
# Operations
## Report Access and Generation
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> On the top menu of your Jira Data Center instance, click *Projects* (Figure 2 - 1) and select a project (Figure 2 - 2).
>
> 
>
> > Macro (rw-step)
>
> A menu will open on the left side of the screen. There, click *Xray* *Reports* (Figure 2 - 3).
>
> > Macro (rw-step)
>
> Use the dropdown menu at the top of the screen (Figure 3 - 1) and click the *Test Runs Report* (Figure 3 - 2).
>
> 
>
> > Macro (rw-step)
>
> Click the *Generate Report* button (Figure 3 - 3) to create the report.
>
> > Macro (rw-step)
>
> The report will be instantaneously generated (Figure 4).
>
> 
## Understanding and Using the Report
### Columns
The Test Runs Report operates on a** **column-based customization system:
- **Default Columns**: the system provides standard columns (Key, Summary, Status, etc.; Figure 4 - 1). Click *Columns* (Figure 5 - 1) and then *Restore Defaults* (Figure 5 - 3) to restore the default columns.
Click the *Columns* button (Figure 5 - 1) first to access these options:
- **Non-Default Columns**: additional fields available but hidden by default (Figure 5 - 2).
- **Column boxes**: check/uncheck to select which columns to display (Figure 5 - 3). Choosing or deselecting columns from the dropdown menu will also affect the columns displayed in the table (Figure 4 - 1).
- **Column reordering**: click the grey dots to drag-and-drop and rearrange columns (Figure 5 - 4). You can also do this directly on the table (Figure 6 - 1) by dragging the column up or down to the desired position and releasing/dropping it in the new position. This action has the same effect as rearranging columns within the column dropdown menu, and changes made in one area will be reflected in the other.
> ⚠️ Click *Done* (Figure 5 - 5) to implement these changes. Your configuration is saved and persists across sessions.
### Source Data
Source Test Runs objects (Figure 7 - 2) can be directly provided using a Test Execution or Sub-Test Execution-based saved filter or by specifying some Test and Test Execution fields.
Available by clicking *Project* (Figure 7 - 1).
Once you’re finished, click *Apply* (Figure 7 - 3) to save your changes.
- **Project**: select one or multiple projects to analyze **(only available in Xray Enterprise).**
- **Fix Version**: the Test Execution Fix Version.
- **Revision: **the Test Execution Revision.
- **Test Environments: **the Test Environments of the Test Execution.
- **Test Plan**: the Test Plan from the Test Execution (when the Test Execution is created within the context of a Test Plan).
- **Test Priority**: the Test Priority.
- **Test Components**: the components field of the Test.
- **Test Run Assignee**: the assignee for each Test Run, and is positioned after the *Summary* column by default. It will show the assigned user name with an icon.
- **Executed By**: the user who executed the Test Run.
- **Status**: the Status of the Test Run. There are different colors for the status:
| **Color** | **Status** | **Description** |
| --- | --- | --- |
| Green | PASS | Test passed successfully |
| Red | FAIL | Test failed |
| Blue | EXECUTING | Test currently running |
| Grey | TODO | Test not yet executed |
| Orange | Aborted | Test not yet aborted |
- **Issue Key or Summary**: Test Execution Key or Test Execution Summary sub-string.
> ℹ️ - Only Test Executions from the selected projects are considered.
> ℹ️ - For performance reasons, Xray limits the number of Test Runs shown to 10,000. If the number of filtered Test Runs is greater than this, you have to review the applied filter and restrict it further.
###
Other Columns (Figure 8 - 1)
- **Test**: key of the Test associated with the Test Run.
- **Components**: components of the Test associated with the Test Run.
- **Test Type**: Type of the Test Associated with the Test Run.
- **Executed By**: the user who performed the execution.
- **Started At**: date of the Test Run start.
- **Finished At**: date of the Test Run end.
- **Elapsed Time**: elapsed Time since the start of the TestRun. If the Status is not final, then the elapsed time will be the time between the start date and the current time.
- **Custom Fields**: the Test Runs Custom Fields. These are configured in the project configuration section. This is a non-default column, and it can be hidden.
- **Text Execution**: key of the Test Execution associated with the Test Run.
- **Fix Version**: fix version associated with the Test Run.
- **Linked Defects**:
- Defects directly associated with the Test Runs. Will count as unique Defects (I.e., if the same Defect Issue is added multiple times in the same Test Run, it will count as one).
- Defects with resolution will be counted as *Closed*; all others will be counted as *Open*.
- **Iterations Progress**: the execution status of a Test Run that contains multiple iterations. This is a non-default column, and it can be hidden.
## Exporting the Report
Once generated, the report can be exported to a CSV file, which will include all report rows (and not just the visible ones):
> Macro (rw-ui-steps-macro)
>
> > Macro (rw-step)
>
> Click *Export* (Figure 9 - 1) and then *To csv* (Figure 9 - 2).
>
> 
>
> > Macro (rw-step)
>
> You will get the file on your machine instantaneously.
## Highlights
The Test Runs Report includes an interactive onboarding system to help you discover and understand new features. This includes:
- **Reports menu lozenge** - *NEW* tag in the reports dropdown menu (Figure 10 - 1).
- **Onboarding cards** - dismissible information cards for each report type (Figure 10 - 2).
- **Feature highlights** - contextual tool tips and hints (Figure 10 - 2).
> Macro (rw-ui-expands-macro)
>
> > Macro (rw-expand)
>
> If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301501383).