Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Do
-
R3.1.4
-
None
-
None
Description
These are the steps to replicate the problem
1. On Jira, I have a filter of only Test Executions like TEST-123, TEST-124, TEST-125. Each one have 3 different Cucumber Test cases in it. 2. On Jenkins, I used the above filter in "Add build step" "Xray: Cucumber Features Export Task" as first step in the job. 3. Executed the relevant cucumber Test cases, total of 9 through Automation tool and it generated the Cucumber JSON report 4. Now, Using "Post-build Actions", I passed the Cucumber JSON report path to import the execution details. 5. When I checked on JIRA after completion of Jenkins Job execution, I see the first Test Execution i.e, TEST-123 now have all the 9 Cucumber Test case execution details. Other 2 Test Executions don't have any update whatsoever. This is same even if I pass 2 different Test Execution Issue Keys as parameters at "Add build step" "Xray: Cucumber Features Export Task" level.
Summarizing:
Using Jenkins, when exporting feature files from Cucumber Tests, each already associated with a specified Test Execution, executing them through a Jenkins job, and then importing the Job results, all the results will be imported to the first Test Execution tagged, regardless of the Cucumber Test was even associated with it to begin.