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
  • Plugin configuration

Was this helpful?

  1. Reference
  2. Configuration reference

toolSettings

This configuration section contains settings for the synchronization tool.

The following example shows the available options within this section.

{
  ...
  "toolSettings": {
    "licensePath": "specsync.lic",
    "disableStats": false,
    "outputLevel": "normal",
    "parentConfig": "specsync-common.json",
    "ignoreParentConfig": false
  }, 
  ...
}

Settings

Setting
Description
Default

licensePath

specsync.lic

evaluationMode

If set to true, SpecSync will not fail when the license scenario limit is reached but completes the synchronization up to the limit.

false

disableStats

false

outputLevel

normal

parentConfig

not specified, the files in the parent folder will be considered

ignoreParentConfig

false

logFile

no log file

allowDownloadingThirdPartyPlugins

If set to true, SpecSync is allowed to download plugin packages created by 3rd parties from nuget.org or the specified package source.

false

pluginCacheFolder

Custom plugin cache folder to be used by SpecSync to download plugin packages.

plugins stored in the SpecSync app data folder

disablePluginCache

If set to true, SpecSync will always download or extract the plugin package even if the same plugin package version has been used already. This is useful for testing plugins.

false

plugins

no plugins

forceProcessingRemovalsOnFilter

false

doNotSynchronizeAutomationUnlessEnabled

false

Plugin configuration

Setting
Description
Default

packageId

The ID of the plugin package (NuGet)

either this or assemblyPath is mandatory

packageVersion

The full version of the plugin package

mandatory, if packageId is specified

packageSource

he package source (NuGet v3 feed or local folder) to be used to download the plugin package.

uses nuget.org feed

assemblyPath

The path for the SpecSync plugin assembly (dll file) when the plugin is not loaded from NuGet package

either this or packageId is mandatory

parameters

Optional parameters for the plugin in key-value pairs. Please contact the maintainer of the plugin for the specific values.

PreviousConfiguration referenceNextlocal

Last updated 1 month ago

Was this helpful?

Path for the license file. Can contain an absolute or a relative path to the config file folder. It may contain environment variables in ...%MYENV%... form. Can be overridden by the --license . See for details.

If set to true, SpecSync will not collect anonymous error diagnostics and statistics. Can be overridden by the --disableStats .

Set the detail level of error messages and trace information displayed by the tool. Available options: normal, verbose and debug. Can be overridden by the --verbose .

Path for the parent config file. See for details.

If set to true, SpecSync will not apply the configuration settings of the config files in the parent folders or the user-specific configuration settings. See for details.

Path for the log file to be created. Can be overridden by the --log .

An array of . See for details.

If set to true, SpecSync will process removed local test cases (ie. add tag and remove from ), even if the synchronization is filtered.

If set to true, SpecSync will not synchronize the automation-related fields of the Test Case unless the synchronization/automation/enabled is set to true. With this setting, the automation fields can be updated by other tools or set using the feature.

These settings can be used in the toolSettings/plugins array. See for details.

SpecSync Plugins
Configuration reference
Hierarchical configuration files
Hierarchical configuration files
Hierarchical configuration files
remote scope
SpecSync Plugins
plugin configurations
Licensing
command line option
command line option
command line option
command line option
Update Test Case fields