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
  • Excluding scenarios using tags
  • Excluding scenarios by specifying feature files

Was this helpful?

  1. Features
  2. Common synchronization features

Excluding scenarios from synchronization

PreviousInclude synchronized Test Cases to a Test Suite (deprecated)NextSynchronization conflict resolution

Last updated 2 months ago

Was this helpful?

By default all scenarios in all feature file of the are included in the synchronization, but SpecSync can be configured to exclude certain scenarios by specifying the local scope.

The local scope should be used to permanently exclude some scenarios from the synchronization (e.g. the ones that are tagged with @ignore). In order to temporarily skip scenarios for a particular synchronization command execution, you can use the filtering function instead. See for details.

Excluding scenarios using tags

The most common way to restrict the local scope is by using scenario tags. By specifying a tag expression for the local/tags configuration setting, you can restrict the synchronization scope. (See also the reference documentation of the ).

The following example sets the local scope to the scenarios that are marked as @done but exclude the ones that are tagged with @ignored or @planned.

{
  ...
  "local": {
    "tags": "@done and not (@ignored or @planned)"
  },
  ...
}

Excluding scenarios by specifying feature files

This feature is supported in SpecSync v3.3 or later.

If the configured folder or .NET project also contains feature files that you don't want to include in synchronization, you can also restrict the local scope by specifying the set of feature files. For this you need to specify one ore more path expressions () in the local/sourceFiles configuration setting. (See also the reference documentation of the ).

The following example sets the local scope to the scenarios that only files from Folder1 and files with name start with alpha from Folder3 are included in the synchronization.

{
  ...
  "local": {
    "sourceFiles": [
      "Folder1/",
      "Folder3/**/alpha*.feature"
    ]
  },
  ...
}

Besides standard glob expressions, the settings can also contain logical expressions as well, e.g. Folder1/*.feature and not **/B.feature. File paths containing white spaces have to be wrapped with quotes (") or apostrophes ('), e.g. 'My Folder/A.feature'. To see all options to express the conditions, please check .

local feature-set
Filters and scopes
local configuration section
glob patterns
local configuration section
Local test case conditions