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
  • Supported Azure DevOps systems
  • Supported operating systems and platforms
  • Supported BDD tools
  • Supported test result formats
  • Supported SpecFlow versions
  • Supported Reqnroll versions
  • Supported SpecFlow versions for test-suite based execution

Was this helpful?

  1. Reference

Compatibility

PreviouscustomizationsNextOlder versions

Last updated 1 month ago

Was this helpful?

Supported Azure DevOps systems

SpecSync for Azure DevOps might work with other Azure DevOps installations as well, but it has been tested with the following configurations:

  • Azure DevOps Services (Visual Studio Team Services, VSTS, VSO)

  • Azure DevOps Server 2022 (Version 19.*)

  • Azure DevOps Server 2020 (Version 18.*)

  • Azure DevOps Server 2019 (Version 17.*, Dev17.*) — up to SpecSync v3.4

  • Team Foundation Server 2018 (Version 16.*) — up to SpecSync v3.4

  • Team Foundation Server 2017 (Version 15.*) — up to SpecSync v3.4

  • Team Foundation Server 2015 Update 3 (Version 14.*) — up to SpecSync v2.1

  • Team Foundation Server 2013 Update 1 (Version 12.*) — up to SpecSync v1.3

The Azure DevOps team (cloud version). As the Azure DevOps client library SpecSync uses for v2.1 or earlier uses TLS 1.1 by default you will get an error. To be able to use SpecSync v2.1 and earlier versions with Azure DevOps Services, you need to set the remote/securityProtocol setting to Tls12.

To use SpecSync with localized Azure DevOps processes (where the names of the work item types are translated), the name of the Test Case and the Test Suite work item has to be specified in the remote/azureDevOps/testsRelationName and remote/azureDevOps/relatedRelationName configuration settings.

Supported operating systems and platforms

SpecSync is supported on Windows, Linux and MacOS operating systems. It can be installed as a standalone tool or as a .NET tool. Please check for details on which installation option is available on the different target systems.

SpecSync does not use Log4J and therefore it is not affected by the vulnerability .

Supported BDD tools

Supported test result formats

BDD Tool
Runner
Extension
Format specifier

SpecFlow/Reqnroll

MsTest

TRX

trx

SpecFlow/Reqnroll

NUnit

TRX

trx

SpecFlow/Reqnroll

xUnit

TRX

trx

SpecFlow

SpecFlow+ Runner

TRX

trx

SpecFlow

NUnit

XML

specFlowNUnitXml

SpecFlow

NUnit v2

XML

specFlowNUnit2Xml

Reqnroll

NUnit

XML

reqnrollNUnitXml

Reqnroll

NUnit v2

XML

reqnrollNUnit2Xml

Reqnroll

Cucumber Messages output

NDJSON

cucumberMessagesNdjson

Cucumber (Java, JavaScript, Ruby)

json formatter

JSON

cucumberJson

Cucumber (Java, JavaScript, Ruby)

message formatter

NDJSON

cucumberMessagesNdjson

Cucumber Java

JUnit

XML

cucumberJavaJUnitXml

Cucumber Java

Surefire

XML

cucumberJavaSurefireXml

Cucumber.js

cucumber-junit-formatter

XML

cucumberJsJUnitXml

JSON

cypressCucumberJson

Jest

jest-cucumber

XML

jestCucumberXml

Python Behave

XML

pythonBehaveXml

PyTest.BDD

XML

pyTestBddXml

Cucumber Studio (Hiptest)

JSON

hiptestJson

Supported SpecFlow versions

Synchronizing scenarios from SpecFlow projects and publishing test results is supported for any SpecFlow versions.

Supported Reqnroll versions

Supported SpecFlow versions for test-suite based execution

  • SpecFlow v4.0 (up to SpecSync v3.4)

  • SpecFlow v3.9 (from SpecSync v3.2.6)

  • SpecFlow v3.8 (up to SpecSync v3.4)

  • SpecFlow v3.7 (up to SpecSync v3.4)

  • SpecFlow v3.6 (up to SpecSync v3.4)

  • SpecFlow v3.5 (up to SpecSync v3.4)

  • SpecFlow v3.4 (up to SpecSync v3.4)

  • SpecFlow v3.3 (up to SpecSync v3.4)

  • SpecFlow v3.1 (up to SpecSync v3.4)

  • SpecFlow v3.0 (up to SpecSync v3.3)

  • SpecFlow v2.4 (up to SpecSync v3.2)

  • SpecFlow v2.3 (up to SpecSync v3.2)

  • SpecFlow v2.2.1 (up to SpecSync v1.4)

For test-suite based execution, Azure DevOps supports only MsTest officially, but the plugins work also with MsTest, NUnit and xUnit.

SpecSync can synchronize any scenarios that are written in Gherkin format. Gherkin format is used by many tools in many platforms, like Cucumber, Cucumber JVM, Cucumber.js, Behat, Behave, SpecFlow and also Reqnroll. Please refer to the for detailed instructions how to setup SpecSync with the different BDD tools.

The test results can also be re-published from a Test Run, published by any supported TRX-based tool using the testRunTrx format specifier. See for details.

Other test result formats are added on request. Please .

Synchronizing scenarios from projects and publishing test results is supported for any Reqnroll versions.

To be able to use the legacy method, a special SpecFlow plugin has to be used that is specific to a particular SpecFlow version. This plugin is provided for the following SpecFlow versions.

See more details on the page.

deprecated TLS 1.0/1.1 access for Azure DevOps Services
Installation & Setup
CVE-2021-44228
Getting started
How to publish test results from pipelines using the VSTest task
contact support
Reqnroll
test-suite based execution
Support for Azure DevOps Test Plan / Test Suite based test execution
Cypress