SpecSync Documentation
Jira
Azure DevOpsJira
Jira
Azure DevOpsJira
  • Introduction to SpecSync for Jira
  • 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
      • 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: Automatically link changed Test Cases
      • Customization: Synchronize linked artifact titles
      • 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
      • Excluding scenarios from synchronization
      • Synchronization conflict resolution
    • Test result publishing features
      • Publishing test result files
    • General features
      • Jira authentication options
      • Configuration file
      • Hierarchical configuration files
      • Local test case conditions
      • Configuration wizards
      • SpecSync plugins
    • Customizations
    • Plugin list
  • Licensing
  • Guides
    • What is my Jira server URL?
    • Jira Test Case Management (TCM) solution
    • How to define the local feature-set to be synchronized
    • Filters and scopes
    • How to use SpecSync from build or release pipeline
    • How to upgrade to a newer version of SpecSync
    • How to attach files to test results
    • 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
    • Migrating from SpecSync v1 to v5
  • Changelog
  • Release Model and Roadmap
  • Downloads
  • Reference
    • Command line reference
      • init
      • upgrade
      • push
      • pull
      • publish-test-results
      • version
    • Configuration reference
      • toolSettings
      • local
      • remote
      • jira
      • knownRemotes
      • synchronization
        • push
        • pull
        • links
        • attachments
        • format
        • fieldUpdates
      • hierarchies
      • publishTestResults
      • specFlow
      • customizations
    • Compatibility
    • Older versions
  • Contact
    • SpecSync Support
    • Troubleshooting
    • FAQ
  • Project Website
Powered by GitBook
On this page
  • Supported Jira systems
  • Supported operating systems and platforms
  • Supported BDD tools
  • Supported test result formats
  • Supported SpecFlow versions
  • Supported Reqnroll versions

Was this helpful?

  1. Reference

Compatibility

PreviouscustomizationsNextOlder versions

Last updated 1 month ago

Was this helpful?

Supported Jira systems

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

  • Jira Cloud

  • Jira Server / Data Center v9

  • Jira Server / Data Center v8

  • Zephyr Scale Server / Data Center v9

For the different supported Test Case Management (TCM) solution, please check the guide.

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

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.

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

Other test result formats are added on request. Please .

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

Jira Test Case Management (TCM) solution
Installation & Setup
CVE-2021-44228
Getting started
contact support
Reqnroll
Cypress