---
title: "Test Execution"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44565117/Test%20Execution"
format: markdown
---
> Macro (ui-expand)
>
> > Macro (toc)
# Introduction
A Test Execution is an Issue type that aggregates a user-determined collection of [Tests](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565156). It monitors and verifies if those Tests are working as expected in a target context and [environment](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565129).
The Overall Execution Status, updated as each Test is performed, informs you about the progress of the Test Execution, including which Tests passed, failed, are being executed, or are waiting to be performed.
An association between a Test Execution Issue and a Test Issue is called a [Test Run](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565109).** **Hence, a Test Execution is a list of Test Runs.
A Test Execution Issue can be assigned to a Tester. It is also possible to assign individual Test Runs to several Testers.
> ℹ️ **Sub Test Execution**
> ℹ️
> ℹ️ You can [create a Test Execution as a Sub-Task](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565114) in the Requirement Issue View Page.
# Access
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
# Sections
## Fields
A Test Execution has the following custom fields:
- Details (Figure 2 - 2):
- Assignee/reporter.
- Labels.
- Priority.
- Xporter - Tests.
- [Test Plans](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565153).
- Test Environments (environments in which the Test Run is executed).
- More Fields (Figure 2 - 3):
- Original estimate.
- Time tracking.
- Components.
- Sprint.
- Team.
- Fix versions.
- Parent.
- Automation (Figure 2 - 4): you can see the recent runs.
You can also use this section to change the Issue's status (Figure 2 - 1), perform actions, and configure the layout of these fields (Figure 2 - 5). You can also see the information regarding the creation and update date of the Issue (Figure 2 - 4).
## Tests Section
### Overall Execution Status
Here, you can:
- Add Tests (Figure 3 - 1).
- Check a colored progress bar where you can see the status of a Test Execution (Figure 3 - 2). Final statuses float to the left side; the last status color to appear is the *To Do* status. You can also see the status of each Test (Figure 3 - 8).
- See the Tests that belong to the Test Execution (Figure 3 - 7).
- Filter the Tests (Figure 3 - 3; 4). You filter Test Runs by Assignee, Status, Test Set, Components, or open text. It is also possible to add other fields to the filter by clicking the *More* button and selecting the fields you want.
- Perform actions on each Test (Figure 3 - 6), such as: assigning, changing rank, opening the dataset, archiving, removing the Issue, and executing it with the [Xray Exploratory App](https://www.getxray.app/exploratory-testing). More of these operations below.
# Operations
## Issue Screen/Fields
### Creating a New Test Execution
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Editing a Test Execution
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Cloning a Test Execution
When cloning a Test Execution Issue, all the Test issue associations will also be cloned. However, a new Test Run is created for each Test so that the new Test Execution Issue has no execution state.
Test Environment associations will be cloned as well.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ℹ️ Once the cloned Issue is created, it will be opened. On some occasions, the cloned Issue screen may open before the Xray information is cloned and, as a result, the new Test Execution will appear empty. When this happens, a warning message will appear (Figure 8).
> > ℹ️
> > ℹ️ 
### Deleting a Test Execution
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Moving a Test Execution
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Document Generator
> ℹ️ You have to enable the Document Generator option on the [Xray global settings](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566331), to use it.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Exporting to Cucumber
> ℹ️ [Cucumber](https://cucumber.io/) Test Executions in Jira can be exported as .feature files ready to be executed in Cucumber. The generated `.feature` files follow the rules defined in [Export Rules](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565307) and consider the context of the Jira Test Execution Issue.
> ℹ️
> ℹ️ A single Cucumber `.feature` file must be generated and prompted to be downloaded for the Cucumber Test contained on the Test Execution, unless the target Test Execution contains multiple Cucumber Tests or the Cucumber Test is associated with multiple **Requirements. **In this case, a **FeatureBundle** ZIP file will be generated containing a single Cucumber feature file for every Requirement associated with the target Cucumber Test contained in the Test Execution.
> ℹ️
> ℹ️ See [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44572481) to learn more about the Cucumber settings in the Xray global settings.
To export a Test Execution Issue containing Cucumber Tests to .feature files:
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Importing Execution Results
[Automated](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565278) Execution Test results can be imported from JSON/XML external files that must follow an [Import Results](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565311) specific scheme.
When importing results, only the Tests contained in the intersection between the Tests in the JSON/XML file and the Tests in the selected Test Execution are updated; all others, if any, are ignored. After importing, a new entry with the result of the operation is registered in the Activity Log of the Test Run.
To import Execution Test results:
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
## Tests
### Adding Tests
Tests and Test Sets can be associated with Test Execution Issues.
#### Existing Tests
To add Test Issues to a Test Execution:
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
#### Tests from Test Sets
When adding a Test Set Issue to a Test Execution, all the Test Issues associated with that Test Set are added to the Test Execution. The Test Set Issue is not directly associated with the Test Execution, so changes to the Test Set after it was added will not affect the Test Execution.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
#### New Test
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Associating Test Executions with a Test Plan
Associating Test Executions with a [Test Plan](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44578481) in Xray centralizes tracking and simplifies reporting by consolidating results in one place. It improves organization, ensuring all relevant Tests are accounted for, and enhances analysis by providing a clear view of Test status across multiple executions. This leads to better management and control of the testing process.
You can associate Test Executions with Test Plans by editing the field *Test Plans*** **in the Test Plans section in Test Execution Issue details (Figure 3 - 9). With this method, **only the Test Execution will be associated with the Test Plan; the Tests will not be associated**. To inline edit the** ***Test Plans*** **field, just hover over the field view area, click it, and add or remove the Test Plans.
> ℹ️ If the Test Execution is associated with a Test Plan and contains Tests that are not in the Test Plan, a warning message will be displayed telling you how many tests in the Test Execution are not in the Test Plan. An *Add Tests* button will be presented, in that message, in case you want to add these Tests to the Test Plan.
> ℹ️
> ℹ️ There will be one warning message for each Test Plan associated with the Test Execution that does not contain all the Tests in the Test Execution.
### Removing Tests
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Assigning Work
There are two ways to distribute work between Testers.
- A Test Execution Issue can be created per Tester by assigning the Issue to a specific Tester (Figure 28 - 1).
- Within a Test Execution Issue, you can assign individual Test Runs to Testers. Test Runs are assigned to the Test Execution Issue assignee by default. Only users with permission to assign the Test Execution issue can assign Test Runs. More below.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ℹ️ After assigning a Test Run, an email notification is sent to the new assignee if the corresponding setting is enabled in the [Global](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566331) or [Project Settings](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44568490).
### Ordering / Ranking
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Archiving a Single Test Run
Xray provides you with a way to explicitly [archive Test Runs](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44571909) one at a time or in bulk (more below), as well as a way to check all the archived Test Runs for a specific Test execution.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Dataset
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Executing with the Xray Exploratory App
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Executing a Test
> ℹ️ If you do not have permission to execute the Test Run, the *Execute* icon (Figure 38 - 2) will not be available.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
#### Executing a Test Inline
To execute Test Runs inline from the Test Execution screen (Figure 39), this option must be enabled in the [Xray administration](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566331) screen. The option to [set the Test Run status manually](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566331) without having to execute all [Test Steps](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565316) (or Examples, in the case of Cucumber Tests) must also be enabled in the Xray administration screen.
If the above options are enabled and you have permission to execute the Test, the context menu for executing Test Runs, accessed by the **Gear** button on each Test will show the available transitions.
When executing inline Tests, the status of the Manual Steps (or Examples, in the case of Cucumber Tests) can be changed automatically. The following rules are applied:
- **PASS**: all step statuses will be changed to PASSED independently of their current status.
- **FAIL**: all step statuses will remain unchanged, even if they are all PASSED. This is because a Test might fail due to a [Precondition](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565159).
- **TO DO**: All step statuses will be changed to TODO. ** **
- **EXECUTING**: The Test Execution status will be changed to EXECUTING.
- **CUSTOM**: The Test Execution status will be changed to the specified custom status.
To execute a Test Run inline:
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Viewing Tests Details
You can always view and modify the Test Run details after execution. If you do not have permission to execute the Test Run, you can still view the execution details in read-only mode, provided you have permission to browse the Test Execution Issue.
To view the execution details from a Test Run:
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Bulk Operations
Xray provides the following bulk operations on the Test Runs table:
- **Assign - **assigns all the selected Test Runs to a particular user.
- **Archive - **archives all the selected Test Runs.
- **Delete - **deletes all the selected Test Runs.
- **Execute** - execute all the selected Test Runs.
To execute these bulk actions:
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ℹ️ The Bulk execution of Test Runs is limited to a maximum of 100 Test Runs.
#### **Viewing Archived Test Runs**
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Filtering
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
### Configuring Columns
Columns of the respective Test Issue of each [Test Run](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565109) can be added/removed. Test Run custom fields can also be added, they are prefixed by "TestRun", so, for example, a Test Run custom field named "User", can be found under the name "TestRun User".
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
## Xray History
Any changes made to the Test Execution data are recorded in the Xray History section (Figure 51). These include:
- Linking the Test Execution with other entities (Tests and Test Plans).
- Changing Test Environments.
- Etc.
Support/Troubleshooting
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/XRAYCLOUD/pages/44577312).