publish-test-results

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 Publishing test result files page. Please also check the related configuration file reference for the publish-test-results command.

Options

In addition the the options listed here, all common command line options can also be used.

Option	Description	Default
--tagFilter	A local test case condition of scenarios that should be considered for test result publishing (e.g. @current_sprint and @done). See Filters and scopes for details.	not filtered by tags
--sourceFileFilter	An expression of source file glob patterns that should be considered for test result publishing (e.g. Folder1/**/*.feature). See Filters and scopes for details.	not filtered by feature files
-r|--testResultFile <FILE‑PATH>	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 glob pattern syntax.	use from config file
-f|--testResultFileFormat <FORMAT>	The file format of the file to publish. Please check the Compatibility page for supported formats. Invoking the command with ? as format will list all supported format as well.	use from config file or detect automatically
--runName <NAME>	The name of the Test Run to be created. The value can contain placeholders.	get from test result file
--runComment <RUN‑COMMENT>	The comment field of the test run to be created. The value can contain placeholders.	not specified
--testResultComment <RESULT‑COMMENT>	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 placeholders.	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>	Additional settings for the test run to be created. The value can contain placeholders. 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".	name field is loaded from test result file, the others are not specified
--testResultSetting <NAME>=<VALUE>	Additional settings for the individual test results. The value can contain placeholders. 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".	not specified

Examples

Publishes a test result file result.trx to Jira:

dotnet specsync publish-test-results --testResultFile result.trx

Publishes a test result file produced by Cucumber Java JUnit execution:

dotnet specsync publish-test-results --testResultFile cucumber-result.xml --testResultFileFormat CucumberJavaJUnitXml

Publishes test results to Jira with Zephyr Scale and set Test Cycle folder and result environment.

dotnet specsync publish-test-results -r result.trx --testRunSetting "folder=/MyFolder" --testResultSetting "environment=Chrome"

Command line referencepublishTestResults