Document Generator allows you to get following data from the Xray Test Execution:
If a Test Execution contains a lot of information, it can decrease Jira performance
Overall Execution Status
Export the Overall Execution Status with name and percentage for each Test Execution Status
${Overall Execution Status}
You can print the status of the Test Execution by using the following notation:
% per Status | Number of Tests per Status |
---|---|
${Overall Execution Status.NameOfStatus} | ${Overall Execution Status.NameOfStatus.Count} |
See the real example:
Iterating Test Runs associated with a Test Execution
Xporter for Jira allows rendering of all the Test Tuns associated with a Test Execution.
Definition:
$ {TestRuns[n].Field} |
n is the index of the Test Run, starting from 0. The field TestRunsCount was created in order to give the total number of Test Runs.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
Exporting Test Runs custom Fields
To export Test Runs Custom Fields you just have to defined the placeholder with the name of you custom field.
Example: Image that you have a custom field called "Run CF". To get the value printed on you document you just have to use the following placeholder:
#{for testrun} The Run CF value is: ${TestRun[n].Run CF} #{end}
If your custom field type is a Number, Data or Date Time you can use formatting functions.
Iterating Pre-Conditions associated with a Test Run
Xporter for Jira allows rendering of the Pre-Conditions associated with a Test from a Test Run.
Definition:
$ {TestRuns[n].PreCondition.Field} |
n is the index of Test Runs, starting from 0. The fields available for Pre-Conditions are:
- Key
- Summary
- Conditions
- Pre-Condition Type
Iterating Attachments associated with a Test Run
Xporter for Jira allows rendering of all the Attachments associated with a Test Run.
Definition:
$ {TestRuns[n].AttachmentsCount[sa]} |
sa is the index of the Attachments, starting from 0. The field AttachmentsCount was created in order to give the total number of Attachments of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
If a Test Execution contains a lot of information, it can decrease Jira performance
Iterating Evidences associated with a Test Run
Xporter for Jira allows rendering of all the Evidences associated with a Test Run.
Definition:
$ {TestRuns[n].ExecutionEvidences[d]} |
d is the index of the Evidences, starting from 0. The field ExecutionEvidencesCount was created in order to give the total number of Evidences of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
Iterating Defects associated with a Test Run
Xporter for Jira allows rendering of all the defects associated with a Test Run.
Definition:
$ {TestRuns[n].ExecutionDefects[e]} |
e is the index of the defects, starting from 0. The field ExecutionDefectsCount was created in order to give the total number of Defects of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
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.
Definition:
Cucumber Scenario: $ {TestRuns[n].Cucumber Scenario} Test Definition: $ {TestRuns[n].Generic Test Definition} |
n is the index of the Test Runs, starting from 0. The fields Cucumber Scenario/Generic Test Definition were created in order to give the step details of Automated Tests of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
If a Test Execution contains a lot of information, it can decrease Jira performance
Iterating Manual Test Step details associated with a Test Run
Xporter for Jira allows rendering of the Details from Manual Tests associated with a Test Run.
Definition:
$ {TestRuns[n].TestSteps[r]} |
r is the index of the Test Steps, starting from 0. The field TestStepsCount was created in order to give the step details of Manual Tests of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
Iterating Manual Test Step Attachments associated with a Test Run
Xporter for Jira allows rendering of the Attachments from Manual Tests Steps associated with a Test Run.
Definition:
$ {TestRuns[n].TestSteps[r].Attachments[sa]} |
sa is the index of the Test Step Attachments, starting from 0. The field AttachmentsCount was created in order to give the step attachments of Manual Tests of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
If a Test Execution contains a lot of information, it can decrease Jira performance
Iterating Manual Test Step Defects associated with a Test Run
Xporter for Jira allows rendering of the Defects from Manual Tests Steps associated with a Test Run.
Definition:
$ {TestRuns[n].TestSteps[r].Defects[dc]} |
dc is the index of the Test Step Defects, starting from 0. The field DefectsCount was created in order to give the step defects of Manual Tests of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
Iterating Manual Test Step Evidences associated with a Test Run
Xporter for Jira allows rendering of the Evidences from Manual Tests Steps associated with a Test Run.
Definition:
$ {TestRuns[n].TestSteps[r].Evidences[e]} |
e is the index of the Test Step Evidences, starting from 0. The field EvidencesCount was created in order to give the step evidences of Manual Tests of a Test Run.
Since a Test Run isn't a Jira Issue, you can render only the following mappings.
Example:
If you want to export the images, for example ${TestRuns[n].ExecutionEvidences[d].FileURL} you can check here for instructions on how to do it.