SpecSync Documentation
Getting StartedConfigurationGuidesDownloads
Azure DevOps
Azure DevOps
  • Introduction to SpecSync for Azure DevOps
  • Getting started
    • Getting started using SpecFlow
    • Getting started using Cucumber or other Gherkin-based BDD tool
  • Installation & Setup
    • Install as .NET tool
    • Install as .NET Console App
    • Install as native binaries for Linux or macOS
    • Install as Docker image
    • Setup and Configure
  • Features
    • Push features
      • Pushing scenario changes to Test Cases
      • Configuring the format of the synchronized test cases
      • Synchronizing Scenario Outlines
      • Add new Test Cases to an Area or an Iteration
      • Mark Test Cases as Automated
      • Setting Test Case state on change
      • Update Test Case fields
      • Attach files to Test Cases using tags
      • Customization: Setting Test Case fields with default values
      • Customization: Update custom Test Case fields on push
      • Customization: Ignoring marked Test Case steps
      • Customization: Ignoring Test Case Tags
      • Customization: Ignore non-supported local tags
      • Customization: Mapping tags
      • Customization: Synchronizing scenarios from feature branches
      • Customization: Reset Test Case state after change
      • Customization: Automatically link changed Test Cases
      • Customization: Synchronize linked artifact titles
      • Customization: Add Test Cases to Suites
      • Customization: Do not synchronize title
    • Pull features
      • Pulling Test Case changes to local scenarios
    • Common synchronization features
      • Configuration key
      • Remote scope
      • Linking Work Items using tags
      • Synchronizing Test Case hierarchies using Test Suites
      • Include synchronized Test Cases to a Test Suite (deprecated)
      • Excluding scenarios from synchronization
      • Synchronization conflict resolution
      • Re-link scenarios to new Test Cases
    • Test result publishing features
      • Publishing test result files
      • Support for Azure DevOps Test Plan / Test Suite based test execution
      • Customization: Publishing test results to multiple Test Suites
    • General features
      • Azure DevOps authentication options
      • Configuration file
      • Hierarchical configuration files
      • Local test case conditions
      • Configuration wizards
      • SpecSync plugins
    • Customizations
    • Plugin list
  • Licensing
  • Guides
    • What is my Azure DevOps project URL?
    • How to define the local feature-set to be synchronized
    • Filters and scopes
    • How to synchronize automated test cases
    • How to use SpecSync from build or release pipeline
    • How to publish test results from pipelines using the VSTest task
    • How to use the SpecSync Azure DevOps pipeline tasks
    • How to link GitHub pull requests
    • How to upgrade to a newer version of SpecSync
    • How to attach files to test results
    • Using SpecSync with SpecFlow+
    • Using SpecSync with Cucumber
    • Using SpecSync with Cypress
    • Using SpecSync with Postman
    • Using SpecSync with TestNG
    • Using SpecSync on macOS or Linux
    • Using SpecSync inside a Docker container
    • How to handle Test Cases of multiple parallel application releases
    • Migrating from SpecSync v3 to v5
    • Migrating from SpecSync v2 to v3
    • Migrating from SpecSync v1 to v2
  • Changelog
  • Release Model and Roadmap
  • Downloads
  • Reference
    • Command line reference
      • init
      • upgrade
      • push
      • pull
      • publish-test-results
      • re-link
      • version
    • Configuration reference
      • toolSettings
      • local
      • remote
      • knownRemotes
      • synchronization
        • push
        • pull
        • automation
        • state
        • areaPath
        • iterationPath
        • links
        • attachments
        • format
        • fieldUpdates
      • hierarchies
      • publishTestResults
      • specFlow
      • reqnroll
      • customizations
    • Compatibility
    • Older versions
  • Contact
    • SpecSync Support
    • Troubleshooting
    • FAQ
  • Project Website
Powered by GitBook
On this page
  • Settings
  • Setting Placeholders

Was this helpful?

  1. Reference
  2. Configuration reference

publishTestResults

PrevioushierarchiesNextspecFlow

Last updated 2 months ago

Was this helpful?

This configuration section contains settings related to publishing test results.

To read more about publishing test results see the page. Please also check the for the publish-test-results command.

The following example shows the most common options within this section.

{
  ...
  "publishTestResults": {
    "testResult": {
      "filePath": "test-result.trx"
    },
    "treatInconclusiveAs": "Failed",
    "testConfiguration": {
      "name": "Windows 10"
    },
    "testRunSettings": {
      "name": "Acceptance test results"
    },
    "testResultSettings": {
      "comment": "BDD results"
    }
  },
  ...
}

Settings

Setting
Description
Default

testResult

The test result configuration

  • testResult/filePath — The path of the test result file (e.g. TRX) file or a folder containing multiple test result files.

treatInconclusiveAs

Maps the Inconclusive test results. Some test execution frameworks report skipped scenarios as Inconclusive, so they should be mapped to another value, e.g. NotExecuted.

not mapped

publishEmptyResults

Publishes test results even if no matching results found.

false

includeNotExecutedTests

Includes test results that are not executed (outcomes NotExecuted, NotApplicable, NotRunnable, NotImpacted).

false

testConfiguration

Specifies a test configuration within the Azure DevOps project as a target configuration for publishing test results.

  • testConfiguration/name — The name of the test configuration.

  • testConfiguration/id — The ID of the test configuration.

uses the single Test Configuration assigned to the Test Suite

testSuite

Specifies a test suite within the Azure DevOps project to publish the test results for.

test cases are not included to a test suite

testSuite/name

The name of the Test Suite. For suites with non-unique names, please use the testSuite/id or testSuite/path setting.

either name, id or path is mandatory

testSuite/id

The ID of the Test Suite as a number.

either name, id or path is mandatory

testSuite/path

The path of the Test Suite from the root of the Test Plan, separated by / (e.g. Ordering/Card Payment).

either name, id or path is mandatory

testSuite/testPlanId

Deprecated, use 'testPlan' instead.

not specified

testSuite/testPlan

The name or ID of the Test Plan to search or create the test suite in, e.g. My Plan or #1234. (Optional, improves performance)

not specified

testRunSettings

  • testRunSettings/name — The name of the created Test Run. (Default: [load from test result file])

  • testRunSettings/comment — The comment of the created Test Run. (Default: empty)

use default settings

testResultSettings

  • testResultSettings/comment — The comment added to the individual test results within the created Test Run. (Default: empty)

use default settings

Setting Placeholders

Placeholder
Description

{br}

a new line

{env:ENVIRONMENT_VARIABLE_NAME}

The content of the environment variable specified (ENVIRONMENT_VARIABLE_NAME in this example)

{testrun-id}

The ID of the created Test Run

{testrun-url}

The URL of the created Test Run

testResult/fileFormat — The format of the test result file. Please check the page for supported formats. Invoking the publish-test-result command with ? as format as command line option will list all supported format as well.

specified as

Can be overridden using with a .

Specifies additional settings for the created test run. The value can contain .

testRunSettings/runType —Sets the run type of the created Test Run. Possible values: manual, automated. (Default: set to automated when is true)

Specifies additional settings for the created test results. The value can contain .

Publishing test result files
command line reference
Configuration reference
publish-test-results
command line option
command line option
synchronization/automation/enabled
placeholders
placeholders
Compatibility