--- title: "Covering with Tests" canonical: "https://docs.getxray.app/space/XRAYCLOUD/44577575/Covering%20with%20Tests" format: markdown --- > Macro (ui-expand) > > > Macro (toc) # Introduction To manage the [Test](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565156) coverage and status of [Requirements](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565860), individual Tests or groups of Tests can be linked to Jira Issues representing these Requirements. A coverable (i.e., testable) Issue is one whose Issue type is configured at the [project-level settings](https://getxraydocs.atlassian.net/wiki/pages/createpage.action?spaceKey=xraycloud&title=Project%20Settings%3A%20Test%20Coverage&linkCreation=true&fromPageId=44577575) to be handled as a coverable Issue type. These Issues can be covered or validated by Tests, whether manual or automated. Tests can then be [organized](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566566) (i.e., in [Test Sets](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565163)), [planned](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565044) (i.e., in [Test Plans](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565153)), and [executed](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565037) (i.e., in [Test Executions](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565117)). The results of the linked Tests will affect the calculation of the Test coverage status for the covered Issue. Typical examples of coverable Issues include Epic and Story (Figure 1), though the project administrator can define which types are handled this way. # Test Coverage View  The Test Coverage view (Figure 1-1) displays all Tests associated with the covered Issue (e.g., Story, Requirement) and their respective statuses for the chosen analysis scope. In this view, you can create a new Test (Figure 1 - 1) and associate it with the covered Issue or link an existing Test. ![Figure 1 - Test coverage view](media://b9a763ee-16ff-493c-848b-e22848e87f45) # Test Coverage Analysis In this section (Figure 1 - 2), the status of the covered Issue and the linked Tests can be analyzed from multiple perspectives/scopes: *Latest*, (Figure 2 - 1) *Version* (Figure 3) and *Test Plan *(Figure 4). As an example, a user Story targeting version 3.0 can be [analyzed](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565185) based on the executions made for version 3.0 or for those made afterward (e.g., version 4.0). You can also consider the Tests and Test Executions linked to a specific Test Plan. If you're not concerned with exact versions and just want to see the latest run statuses, you can use the analysis by *Latest* (Figure 2 - 1).  Another analysis dimension is the Test Environment (Figure 2 - 2). Here, you can view the status of each Test based on the Test Environment you specified. If this option is selected (Figure 2 - 2), only the statuses of the executions made for that Test Environment are considered. Once you're finished, click the *Apply* button (Figure 2 - 3). > ℹ️ The calculation of the Test status or coverage status for an issue is explained in more detail [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565101). > ℹ️ > ℹ️ The analysis scope selected by the user will be saved in the user preferences and applied to all Issues within the project for that user. **Latest/All Environments** Here (Figure 2), you can see the status of each Test based on the Test Environment you specified in this option (Figure 2 - 2). ![Figure 2 - Scopes](media://3b66e120-4d5a-44ab-8422-2db08024144c) **Version** By clicking *Version* (Figure 3 - 1) you can see the Coverage Status for each version (Figure 3 - 2). ![Figure 3 - Version](media://9714ff32-7a42-4036-a941-7630581b1565) **Test Plan** By clicking *Test Plan* (Figure 4 - 1) you can see the Coverage Status for each of the Test Plans (Figure 4 - 2). ![Figure 4 - Test plan](media://a6856de6-a192-46eb-8892-588e12bf725d) # Operations ## Creating a New Test > Macro (ui-steps) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) ## Associating a Test/Test Set with an Existing Test/Test Set Associating a Test or Test Set with an existing one in Xray allows you to: - Reuse Tests across multiple Test Sets, saving time. - Maintain consistency with the same Test version. - Easily track usage for impact analysis. - Simplify updates, as changes apply to all associated sets. - Enhance coverage analysis across projects. This streamlines testing and ensures uniformity. > Macro (ui-steps) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) ## Creating a New Test Execution/Sub-Test Execution ### New Test Execution > Macro (ui-steps) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content) ### Sub-Test Execution > Macro (ui-steps) > > > Macro (legacy-content) > > > Macro (legacy-content) > > > Macro (legacy-content)
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).