# publish-test-results Publishes local test results to Azure DevOps 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](/specsync/features/test-result-publishing-features/publishing-test-result-files.md) page. Please also check the related [configuration file reference](/specsync/reference/configuration/configuration-publishtestresults.md) for the `publish-test-results` command. See more details about the command in the "Assembly based execution strategy" section of the [Synchronizing automated test cases](/specsync/important-concepts/synchronizing-automated-test-cases.md) article. ## Options In addition the the options listed here, all [common command line options](/specsync/reference/command-line-reference.md#common-command-line-options) can also be used. | Option | Description | Default | | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | | `--filter` | A [local test case condition](/specsync/features/general-features/local-test-case-conditions.md) of scenarios that should be considered for test result publishing (e.g. `@current_sprint and @done`). See [Filters and scopes](/specsync/important-concepts/filters-and-scopes.md) for details. | not filtered by tags | | `--sourceFileFilter` | An expression of source file [glob patterns](https://speclink.me/specsync-glob) that should be considered for test result publishing (e.g. `Folder1/**/*.feature`). See [Filters and scopes](/specsync/important-concepts/filters-and-scopes.md) for details. | not filtered by feature files | | `-r`\|`--testResult` \ | The file path of the test result (.trx, .xml or .json) file to publish or a folder that contains multiple test result files. Can be specified multiple times. The semicolon-separated value list is still supported. Wildcards are supported using the [glob pattern](https://speclink.me/specsync-glob) syntax. | use from config file | | `-f`\|`--testResultFormat` \ | The file format of the file to publish. Please check the [Compatibility](/specsync/reference/compatibility.md#supported-test-result-formats) 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` \ | The name of the Test Run to be created. The value can contain [placeholders](/specsync/reference/configuration/configuration-publishtestresults.md#setting-placeholders). | get from test result file | | `--runComment` \ | The comment field of the test run to be created. The value can contain [placeholders](/specsync/reference/configuration/configuration-publishtestresults.md#setting-placeholders). | not specified | | `--testResultComment` \ | 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](/specsync/reference/configuration/configuration-publishtestresults.md#setting-placeholders). | not specified | | `--testRunSetting` \=\ | Additional settings for the created test run. The value can contain [placeholders](/specsync/reference/configuration/configuration-publishtestresults.md#setting-placeholders). For Azure DevOps you can specify `name`, `comment`, `runType`, `buildId`, `buildNumber`, `buildFlavor`, `buildPlatform`. The build ID is a numeric ID of the build (e.g. `345`) and the build number is the configured build number (e.g. `20200119.1`). This option can be used *multiple times* using the `setting=value` format, e.g. `--testRunSetting "name=My Results"`. | use from config file or defaults | | `--testResultSetting` \=\ | Additional settings for the individual test results. The value can contain [placeholders](/specsync/reference/configuration/configuration-publishtestresults.md#setting-placeholders). For Azure DevOps test results you can specify `comment`. This option can be used *multiple times* using the `setting=value` format, e.g. `--testResultSetting "comment=Details"`. | use from config file or defaults | | `--attachFile` \ | File path that should be attached to the test run additionally. (e.g. `error1.png`) Can be specified multiple times. Wildcards are currently not supported. | only test result file attached | | `-c`\|`--testConfiguration` \ | The Azure DevOps Test Configuration name or ID to publish the results for. For specifying an ID, use `#1234` format. | use from config file or detect automatically | | `--testSuite` \ | A Test Suite name or ID to publish the test results to. For specifying an ID, use `#1234` format. (e.g. `My Suite` or `#1234`) | use from config file | | `--testPlan` \ | The name or ID of the Test Plan to search the Test Suite in. For specifying an ID, use `#1234` format. (e.g. `My Plan` or `#345`) | all Test Plans are scanned through | | `--disablePipelineAssociation` | If specified, the published test results will not be associated to the build or release pipeline. This is useful if the Azure DevOps project of the build is different to the project of the Test Cases. See [Troubleshooting entry](/specsync/contact/troubleshooting.md#pipeline-not-found) for details. | pipelines are associated | ## Examples Publishes a test result file `result.trx` to Azure DevOps: ``` dotnet specsync publish-test-results --testResult result.trx ``` Publishes a test result file produced by Cucumber Java JUnit execution: ``` dotnet specsync publish-test-results --testResult cucumber-result.xml --testResultFormat CucumberJavaJUnitXml ``` Publishes a test result file `result.trx` to Azure DevOps to the configured Test Suite for the Test Configuration `Windows 10`: ``` dotnet specsync publish-test-results --testResult result.trx --testConfiguration "Windows 10" ``` Publishes test results to a specific Test Suite, where the Test Cases related to the executed scenarios are included. Test Plan ID is also specified for better performance. ``` dotnet specsync publish-test-results --testPlan "My Plan" --testSuite "Ordering Tests" --testResult result.trx --testConfiguration "Windows 10" ``` {% content-ref url="/pages/-LVwFCLgktB9AOsohdYl" %} [Command line reference](/specsync/reference/command-line-reference.md) {% endcontent-ref %} {% content-ref url="/pages/HZJCa4u07mhVT8YGnDEf" %} [publishTestResults](/specsync/reference/configuration/configuration-publishtestresults.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.specsolutions.eu/specsync/reference/command-line-reference/publish-test-results-command.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.