publish-test-results
Last updated
Was this helpful?
Last updated
Was this helpful?
Publishes local test results to Jira server as a Test Run, where the results are connected to the synchronized test cases and optionally to a build.
To read more about publishing test results see the page. Please also check the related for the publish-test-results command.
In addition the the options listed here, all can also be used.
--tagFilter
not filtered by tags
--sourceFileFilter
not filtered by feature files
-r|--testResultFile <FILE‑PATH>
use from config file
-f|--testResultFileFormat <FORMAT>
use from config file or detect automatically
--runName <NAME>
get from test result file
--runComment <RUN‑COMMENT>
not specified
--testResultComment <RESULT‑COMMENT>
not specified
--attachedFiles <FILE‑LIST>
Semicolon separated list of file paths that should be attached to the test run additionally. (e.g. error1.png;error2.log) Wildcards are currently not supported.
only test result file attached
--testRunSetting <NAME>=<VALUE>
name field is loaded from test result file, the others are not specified
--testResultSetting <NAME>=<VALUE>
not specified
Publishes a test result file result.trx to Jira:
Publishes a test result file produced by Cucumber Java JUnit execution:
Publishes test results to Jira with Zephyr Scale and set Test Cycle folder and result environment.
A of scenarios that should be considered for test result publishing (e.g. @current_sprint and @done). See for details.
An expression of source file that should be considered for test result publishing (e.g. Folder1/**/*.feature). See for details.
The file path of the test result (.trx, .xml or .json) file to publish or a folder that contains multiple test result files. Multiple paths can be listed, separated by semicolon (;). Wildcards are supported using the syntax.
The file format of the file to publish. Please check the page for supported formats. Invoking the command with ? as format will list all supported format as well.
The name of the Test Run to be created. The value can contain .
The comment field of the test run to be created. The value can contain .
The comment added to the individual test results within the created test run. Useful if the individual test results are typically browsed not through the test run. The value can contain .
Additional settings for the test run to be created. The value can contain . For Zephyr Scale Test Cycles you can specify name, description, iteration, version and folder. This option can be used multiple times using the setting=value format, e.g. --testRunSetting "iteration=Iteration 1".
Additional settings for the individual test results. The value can contain . For Zephyr Scale test results you can specify comment and environment. This option can be used multiple times using the setting=value format, e.g. --testRunSetting "environment=Chrome".