---
title: "Common Mistakes to Avoid in Xray: Test Executions without Test Runs"
canonical: "https://docs.getxray.app/space/ProductKB/46269299/Common%20Mistakes%20to%20Avoid%20in%20Xray%3A%20Test%20Executions%20without%20Test%20Runs"
format: markdown
---
This article aims to explain some Xray Anti-patterns  that can lead to future constrains or even data integrity issues. Please use this information carefully and taking in consideration your own setup and team processes. Anti-Pattern Description Test Executions  with no  Test Runs  can be an indication of lack of formal testing process leading to traceability issues and poor Test coverage. These may be  because Xray is only being used to document Test cases, and not to track Test results.  Solution Should your numbers and frequency of this anti-pattern scale, you should stop and review the current process. Testers might be manually executing without documenting it or associating the evidence to the Test Run, or there's a misunderstanding of the workflow. Audit and Review Process enforcement might be needed whenever you see these pop up. Use the following JQL if you are using Xray Data Center, for overseeing it in your dashboard with Filter Result gadget alike. issuetype = 'Test' and TestRunStatus = "TODO" and createdDate < -7d issuetype =  "Test Execution" AND issue not in testExecutionsWithCompletedTestRunsSince("-7d") and createdDate > -7d Xray   Cloud   users   can   currently   obtain   information   about  this  anti-pattern   using   the   Xray  Document   Generator . Snippet code: &{for issues} 
#{if (%{'${IssueTypeName}'.equals('Test Execution')})} 
#{if (%{'${TestRunsCount}'.equals('0')})} 
${Key} - ${Summary}
#{end}
#{end}
&{end} Reporting As an example you can make use  of  Test Execution List Report  to  be attentive to these anti-patterns since they are directly linked to how your requirements are covered. The example below (Figure 1) is a  Document Generator/Xporter template , it's not a built-in Xray report. Test Execution List Output Example shows Book-519 without a Test run. Figure 1 - Example Automation and Integration If applicable, configure Xray’s CI/CD integrations (e.g., with Jenkins, GitHub, Gitlab) to automatically generate and associate Test Runs when Test Executions are triggered via automation pipelines. This ensures that Test Runs are always created when executing automated tests. To find more information, visit our documentation and Tutorials, as well as the Xray Academy. Xray Academy Please take the  Test Automation with Xray  course in the Xray Academy. Figure 2 - Academy Documentation Test Automation integration possibilities in Xray DC Test Automation integration possibilities in  Xray Cloud Tutorials Test Automation tutorials for Xray DC Test Automation tutorials for Xray Cloud Learn More Revisit our documentation on Test Runs and take advantage of all Xray Features. Test Runs in Xray DC Test Runs in Xray Cloud Xray Academy The Xray  Academy   offers   Xray Essentials for Cloud   &   Xray Essentials for Data Center   Course  to help you get familiarized with how to fill in Test Steps and how to use the Modular Test Functionality. Figure 3 - Academy We encourage your team to go through all the  Xray Academy  courses. If you have questions or technical issues, please  contact the Support team via the Customer Portal (Jira service management)  or  send us a message using the in-app chat .