...
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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
Todo: ${Overall Execution Status.TODO}% (${Overall Execution Status.TODO.Count})
Fail: ${Overall Execution Status.FAIL}% (${Overall Execution Status.FAIL.Count})
Pass: ${Overall Execution Status.PASS}% (${Overall Execution Status.PASS.Count})
Executing: ${Overall Execution Status.EXECUTING}% (${Overall Execution Status.EXECUTING.Count})
Aborted: ${Overall Execution Status.ABORTED}% (${Overall Execution Status.ABORTED.Count}) |
You can also use the translated name of Overall Execution Status to get the same information.
| Language | Translated Name |
|---|---|
| ES | Estado de ejecución general |
| DE | Allgemeiner Ausführungsstatus |
| FR | État d'Exécution Global |
See the example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
Todo: ${Estado de ejecución general.TODO}% (${Estado de ejecución general.TODO.Count})
Fail: ${Estado de ejecución general.FAIL}% (${Estado de ejecución general.FAIL.Count})
Pass: ${Estado de ejecución general.PASS}% (${Estado de ejecución general.PASS.Count})
Executing: ${Estado de ejecución general.EXECUTING}% (${Estado de ejecución general.EXECUTING.Count})
Aborted: ${Estado de ejecución general.ABORTED}% (${Estado de ejecución general.ABORTED.Count}) |
...
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 or TestrunsCount was created in order to give the total number of Test Runs.
...
Xporter for Jira allows rendering of the Pre-Conditions associated with a Test from a Test Run.
Definition:
${TestRuns[n].PreCondition.Field} -
| ||||||
| ${TestRuns[n].PreConditions[p].Field} |
n is the index of Test Runs, starting from 0. The fields available for Pre-Conditions are:
...
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.
...
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.
...
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.
...
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.
...
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 or TeststepsCount was created in order to give the step details of Manual Tests of 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.
...
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.
...
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.
...
Xporter for Jira allows export all the activity of a Test Run.
Definition:
$ {TestRuns[n].ActivityEntries[ac]} |
ac is the index of the Activity entry, starting from 0. The field ActivityEntriesCount was created in order to give the Activity entry of a Test Run.
...
To export all this data, we first need to execute the test run. If we change any data, we need to return to the Execution Page and merge it with the new data.
| Fields | Description |
|---|---|
| IsDataDriven | Returns "true" if the current test run is data-driven; otherwise, it returns "false" |
| Iterations Overall Execution Status.STATUS.Percentage | The percentage of STATUS in the test run iterations |
IterationsOverallExecutionStatus | List of all the statuses in the current test run iteration and their percentages |
| IterationsOverallExecutionStatus.STATUS.Count | The number of STATUS in the test run iterations |
| Parameters | List of the parameters from each test run iteration |
| ParametersCount | Total of Parameters declared in Dataset |
| Info | ||
|---|---|---|
| ||
The field IsDataDriven is going to return TRUE only if the test run has more than one iteration. |
...