---
title: "Sub-Test Execution"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44565114/Sub-Test%20Execution"
format: markdown
---
# <span style="color: #333333">Introduction</span>

A Sub-Test Execution functions similarly to a [Test Execution](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565117) Issue type. The key difference is that Sub-Test Execution is a sub-task issue type and can be created within the context of a Requirement.

Creating a Test Execution as a sub-task of a requirement Issue allows you to track executions on the [Agile board](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565049).

# Creating Sub-Test Executions

> ℹ️ The Sub-Test Execution button (Figure 1 - 2) is displayed only if Xray can create a Sub-Test Execution for the project that the covered Issue is in. This means the sub-task Issue type must be configured for that project, and it must not have any required fields beyond the default ones.


> Macro (ui-steps)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)

> ℹ️ Remember to [associate Tests and Test Sets](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565117) to the Sub-Test Execution.
> ℹ️ 
> ℹ️ Find more about interesting usage scenarios for Sub-Test Executions at [Tips for scheduling executions](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565304).


<details>
<summary>Support/Troubleshooting</summary>

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).
</details>