Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi,
I am looking for a way to import the Tests under a Subtest Execution to another Subtest Execution belonging to a different parent.
Currently what I am doing is searching the issue in TestExecution List in Xray and getting the tests from there, saving a filter in Jira and then importing the Tests using that filter. This is a lot for a QA to execute every time. Hence, looking for a better way to do it without using any external apps.
Thanks in advance!
Regards,
Megha
As far as I know you could just do this by knowing which test cases and selecting/adding them manually. In the sub test execution you could say "add tests" and then choose "existing tests". There is also a JQL option but I guess "tests within a certain sub test execution" cannot be resolved.
My question is:
How do you use sub test executions? As test cases are added to a parent (eg. a story) that test the functionality of that story the sub test execution is automatically created consisting of these tests. BUT: as test cases are standalone standard issues you could also add 1 test case to 2 or more parents (stories). so lets say you have "TestCase 1" which is added to "Story A" as well as to "Story B". Now everytime you create a sub test exection (whether in Story A or Story B) TestCase 1 will be part of the sub test execution.
Please let me know if this helps.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I process that you suggested becomes difficult when there are a lot of tests present. My current solution to this problem is to get a query using the test execution list and use the same while adding tests.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.