--- title: "Executing Tests" canonical: "https://docs.getxray.app/space/XRAYCLOUD/44565037/Executing%20Tests" format: markdown --- A Test Execution is the process that occurs between developing Test scripts and [reporting and analyzing the results](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566291). This activity is more complex than simply [starting a Test](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565047) and monitoring it to ensure it runs as expected. It involves: - **Validating the Test environment**: ensuring that the [Test environment](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565129) accurately represents the production environment. If the environments differ, there is a high probability that the Tests may not work as intended or could provide misleading data. For this reason, the Tests themselves should also be validated to ensure they reflect the intended simulation design. - **Running the Test**: executing the test based on the [plans](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565153) and Test documents, once it is confirmed that the Test target is in the proper state for performance testing. After completing the Test Execution, a brief summary of the test should be compiled and added to the Test log for future reference. Additionally, if the analysis of results leads to new priorities, it is important to modify the Tests, Test designs, and subsequent strategies. - **Generating results and reporting errors**: producing the Test results and reporting any errors to the development team. Xray provides the [Test Execution Issue](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565117), which acts as an assignable task for executing a group of Tests (either manual or [automated](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565278)) and collecting the corresponding test results for a specific project version and environment. A [Sub-Test Execution](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565114) is similar to a Test Execution but is created as a sub-task of a Requirement. Typically, you will create Test Executions from Test Plans or create ad hoc Test Executions directly from a [Test](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565156). Once your Test Executions are created, you're ready to [execute them](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565122). Each time a Test is scheduled for execution, a [Test Run](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565109) is created, and Xray will retain the information related to that specific execution of the specific Test. ## Learn More - [Tips for Scheduling Executions](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565304)
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).