Page History
...
Code Block | ||||
---|---|---|---|---|
| ||||
#Iterating over Test Runs #{for testruns} #Iterating over defects from each test run #{for e=TestRuns[n].ExecutionDefectsCount} Link: @{title=${TestRuns[n].ExecutionDefects[e].Key}|href=${BaseURL}/browse/${TestRuns[n].ExecutionDefects[e].Key}} Summary: ${TestRuns[n].ExecutionDefects[e].Summary} #{end} #{end} |
Iterating
...
Xporter for Jira allows rendering of all the Test Steps Attachments associated with a Test Run.
Definition:
...
a is the index of the Test Steps Attachments, starting from 0. The field TestStepsAttachmentsCount was created in order to give the total of Test Steps Attachments of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
Code Block | ||||
---|---|---|---|---|
| ||||
#Iterating over Test Runs
#{for testruns}
#Iterating over TestSteps Attachments
#{for a=TestRuns[n].TestStepsAttachmentsCount}
Name: ${TestRuns[n].TestStepsAttachments[a].Name}
Author: ${TestRuns[n].TestStepsAttachments[a].Author}
Link: @{title=${TestRuns[n].TestStepsAttachments[a].FileURL}|href=${TestRuns[n].TestStepsAttachments[a].FileURL}}
Size: ${TestRuns[n].TestStepsAttachments[a].Size}
#{end}
#{end} |
Warning |
---|
If a Test Execution contains lots of information it can decrease Jira performance |
Iterating Automated Test details associated with a Test Run
Xporter for Jira allows rendering of the Details from Automated Tests associated with a Test Run.
...