# Compatibility

## Supported Azure DevOps systems <a href="#supported-server-systems" id="supported-server-systems"></a>

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*

{% hint style="warning" %}
The Azure DevOps team [deprecated TLS 1.0/1.1 access for Azure DevOps Services](https://devblogs.microsoft.com/devops/deprecating-weak-cryptographic-standards-tls-1-0-and-1-1-in-azure-devops-services/) (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`.
{% endhint %}

{% hint style="info" %}
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.
{% endhint %}

## 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 [Installation & Setup](https://docs.specsolutions.eu/specsync/installation) for details on which installation option is available on the different target systems.

{% hint style="info" %}
SpecSync does not use Log4J and therefore it is not affected by the vulnerability [CVE-2021-44228](https://github.com/advisories/GHSA-jfh8-c2jp-5v3q).
{% endhint %}

## Supported .NET frameworks for running SpecSync as .NET tool

SpecSync can be run using the following .NET versions as a [.NET tool](https://docs.specsolutions.eu/specsync/installation/dotnet-core-tool):

* .NET 10 (latest, recommended)
* .NET 9
* .NET 8
* .NET 7 — *out of support by Microsoft, not recommended*
* .NET 6 — *out of support by Microsoft, not recommended*
* .NET Framework 4.7.2 — *up to SpecSync v3.4*
* .NET Framework 4.6.2 — *up to SpecSync v3.4*
* .NET 5 — *up to SpecSync v3.4*
* .NET 3.1 — *up to SpecSync v3.4*

{% hint style="warning" %}
The .NET 6 and .NET 7 frameworks are out of support and will [not receive security updates in the future](https://aka.ms/dotnet-core-support). SpecSync versions v6 and later will not run with .NET 6 and .NET 7. Please use SpecSync with .NET 8 or any of the other supported platforms.
{% endhint %}

{% hint style="info" %}
**Important:** The .NET framework used for running SpecSync does not have to be the same as the .NET framework of the synchronized project. For example, you can use SpecSync with .NET 8 to synchronize scenarios from a .NET Framework 4.7.2 project. This applies to any BDD project regardless of its framework (.NET, Java, Python, JavaScript, etc.).
{% endhint %}

## Supported BDD tools

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 [Getting started](https://docs.specsolutions.eu/specsync/getting-started) for detailed instructions how to setup SpecSync with the different BDD tools.

## Supported test result formats

| BDD Tool                                                                                         | Runner                        | Extension | Format specifier          |
| ------------------------------------------------------------------------------------------------ | ----------------------------- | --------- | ------------------------- |
| Reqnroll                                                                                         | MsTest/NUnit/xUnit            | TRX       | `trx`                     |
| Reqnroll                                                                                         | NUnit                         | XML       | `reqnrollNUnitXml`        |
| Reqnroll                                                                                         | Cucumber Messages output      | NDJSON    | `cucumberMessagesNdjson`  |
| SpecFlow                                                                                         | MsTest/NUnit/xUnit            | TRX       | `trx`                     |
| SpecFlow                                                                                         | SpecFlow+ Runner              | TRX       | `trx`                     |
| SpecFlow                                                                                         | NUnit                         | XML       | `specFlowNUnitXml`        |
| SpecFlow                                                                                         | NUnit v2                      | XML       | `specFlowNUnit2Xml`       |
| 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`      |
| [Cypress](https://docs.specsolutions.eu/specsync/important-concepts/using-specsync-with-cypress) |                               | JSON      | `cypressCucumberJson`     |
| Jest                                                                                             | jest-cucumber                 | XML       | `jestCucumberXml`         |
| Python Behave                                                                                    | `--junit`                     | XML       | `pythonBehaveXml`         |
| Python Behave                                                                                    | `-f json` or `-f json.pretty` | JSON      | `pythonBehaveJson`        |
| PyTest.BDD                                                                                       |                               | XML       | `pyTestBddXml`            |
| Cucumber Studio (Hiptest)                                                                        |                               | JSON      | `hiptestJson`             |

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 [How to publish test results from pipelines using the VSTest task](https://docs.specsolutions.eu/specsync/important-concepts/how-to-publish-test-results-from-pipelines-using-the-vstest-task) for details.

Other test result formats are added on request. Please [contact support](https://docs.specsolutions.eu/specsync/contact/specsync-support).

## Supported SpecFlow versions <a href="#supported-specflow-versions" id="supported-specflow-versions"></a>

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

## Supported Reqnroll versions <a href="#supported-reqnroll-versions" id="supported-reqnroll-versions"></a>

Synchronizing scenarios from [Reqnroll](https://reqnroll.net) projects and publishing test results is supported for **any Reqnroll versions**.

## Supported SpecFlow versions for test-suite based execution

To be able to use the legacy [test-suite based execution](https://docs.specsolutions.eu/specsync/features/test-result-publishing-features/support-for-azure-devops-test-plan-test-suite-based-test-execution) 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.

* 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.

See more details on the [Support for Azure DevOps Test Plan / Test Suite based test execution](https://docs.specsolutions.eu/specsync/features/test-result-publishing-features/support-for-azure-devops-test-plan-test-suite-based-test-execution) page.