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
  • Installing SpecSync .NET Console App from NuGet for .NET projects
  • Step 1: Install package
  • Step 2: Create/review a CMD file in order to execute the console app easily from the installation folder (optional)
  • Step 3: Verify installation
  • Installing SpecSync .NET Console App for other development platforms
  • Verify installation

Was this helpful?

  1. Installation & Setup

Install as .NET Console App

PreviousInstall as .NET toolNextInstall as native binaries for Linux or macOS

Last updated 2 years ago

Was this helpful?

This install method is available for Windows machines with .NET Framework v4.6.2 or higher. Other available.

SpecSync can be used as a .NET Framework Windows Console App (SpecSync4AzureDevOps.exe). The tool can be downloaded from NuGet.org (for .NET projects) or as a downloadable zip package for other development platforms.

Installing SpecSync .NET Console App from NuGet for .NET projects

The SpecSync .NET Console App is wrapped as a NuGet package, . The Console App is located in the tools folder of the package.

Step 1: Install package

Installing it to a .NET project is similar to other NuGet packages. You can use the NuGet package manager in Visual Studio or the package management console.

Install-Package SpecSync.AzureDevOps.Console

Since the NuGet package does not contain any library that would be referenced from the project, the package does not have a dependency on the .NET Framework used by the project.

Depending on your project setup, the package has been downloaded and extracted to

  • into the packages folder of your solution: <SOLUTION‑FOLDER>\packages\SpecSync.AzureDevOps.Console.<SPECSYNC‑VERSION>

  • into the global packages folder: C:\Users\<USER>\.nuget\packages\SpecSync.AzureDevOps.Console\<SPECSYNC‑VERSION>

  • into an other folder configured in the NuGet.config file

Step 2: Create/review a CMD file in order to execute the console app easily from the installation folder (optional)

As the package installation folder is pretty complicated to type-in frequently, it is recommended to add a simple command line shell script (SpecSync4AzureDevOps.cmd) that executes the tool from the right folder.

A SpecSync4AzureDevOps.cmd script that executes the SpecSync .NET Console App from the global packages folder might look similar to this (the version number has to be set according to the SpecSync version you use):

@REM Executing SpecSync .NET Console App by forwarding all command line parameters
@REM Note: the version number has to be updated after a SpecSync version upgrade
SET SPECSYNC_VERSION=3.3.8
%HOMEPATH%\.nuget\packages\SpecSync.AzureDevOps.Console\%SPECSYNC_VERSION%\tools\SpecSync4AzureDevOps.exe %*

In case you use NuGet packages from the packages folder of your solution the path in the script has to be changed accordingly.

Step 3: Verify installation

SpecSync is ready to run using the SpecSync4AzureDevOps.cmd script. You can test the installation by checking the installed SpecSync version.

SpecSync4AzureDevOps.cmd version

Installing SpecSync .NET Console App for other development platforms

After extracting the package, the SpecSync4AzureDevOps.exe executable can be found in the tools folder.

Verify installation

You can test the installation by checking the installed SpecSync version. Open a command prompt from your project folder and invoke the following command.

<EXTRACTED-SPECSYNC-FOLDER>\tools\SpecSync4AzureDevOps.exe version

If the correct version number is displayed, you are ready to move on to setup and configure SpecSync for the first synchronization. Check the page for the details.

For a special automated Test Case scenario you might need to install an additional NuGet package to your project. This is usually not necessary even for .NET projects. For details please check the .

The SpecSync .NET Console App can be downloaded directly as a zip file from our website. The download URLs can be found on the page.

If the correct version number is displayed, you are ready to move on to setup and configure SpecSync for the first synchronization. Check the page for the details.

installation options
SpecSync.AzureDevOps.Console
Setup and Configure
Downloads
Setup and Configure
setup instructions