We are delighted to announce that our scenario synchronization tool used by many companies to provide traceability with their BDD scenarios is now also available for Atlassian Jira Software.
The first release already supports the most commonly used scenarios and features but we continue improving the product. Make sure you check the feature availability below. If you have any feedback, question or suggestion, please contact us.
SpecSync for Jira works similarly to SpecSync for Azure DevOps. Therefore for general guidance about the concept, please check out the SpecSync for Azure DevOps overview page and the SpecSync for Azure DevOps documentation.
This page contains further information about:
Supported Systems
Currently SpecSync for Jira supports Jira systems with REST API v3 support, which is available in Jira Cloud currently. We work on supporting Jira Server that will be available soon. Please contact us for more details.
As Jira does not have a built-in Test Case Management (TCM) solution, teams using Jira need to choose from different TCM solutions in Jira. The different solutions require different synchronization solutions, but we are committed to provide support for the TCM solutions of our clients.
The following Jira TCM solutions are currently supported or planned.
| Jira TCM Solution | Support | Description |
|---|---|---|
| Jira TCM Customization | Supported | This solution works with any Jira projects. You need to add a custom issue type to store the Test Cases (e.g. ‘Test Case’) and a custom field in the issue type to store the Test Case steps as formatted text (e.g. ‘Test Case Steps’). Optionally you can also define a custom field for storing the scenario in Gherkin format as well. |
| Xray | Planned for v1.1 | Support for Jira projects using the Xray extension app. |
| Zephyr Squad | Planned for v2 | Support for Jira projects using the Zephyr Squad extension app (formerly Zephyr for Jira). |
| Zephyr Scale | Planned for v2 | Support for Jira projects using the Zephyr Scale extension app (formerly Test Management for Jira, TM4J). |
Pricing & Orders
The pricing model of SpecSync for Jira is similar to SpecSync for Azure DevOps. You can purchase subscriptions for teams. The base subscription package provides a subscription for 3 teams, but you can buy additional extensions for further teams.
SpecSync for Jira offers three editions:
- Free – SpecSync for Jira standard features can be used without subscription for free, for synchronizing up to 30 scenarios.
- Standard – The Standard edition can be used for up to 300 scenarios and includes unlimited email support and 2×30 min online support per year.
- Enterprise – The Enterprise edition allows you to use all the standard and enterprise features without limitation. The subscription includes unlimited priority email support and 5×30 min online support per year.
The SpecSync for Jira license allows you to use the product for 1 year:
- Standard: €990 + VAT for 3 teams / year; €299 per additional teams / year
- Enterprise: €2490 + VAT for 3 teams / year; €749 per additional teams / year
Please contact us for questions or license inquiries!
Feature Availability
The list below contains all the features of SpecSync for Azure DevOps and their availability or limitations in SpecSync for Jira.
Generic features
| Feature | Support | Comment |
|---|---|---|
| Authentication options | Supported | API Tokens (Atlassian account settings / security) |
| Configuration file | Supported | |
| Hierarchical configuration files | Supported | |
| SpecSync Plugins | Supported | Test result publishing related services are not used.Existing SpecSync ADO v3 plugins source-code compatible, but need to be compiled with SpecSync.Jira.PluginDependency package. |
Features related to the “push” command
| Feature | Support | Comment |
|---|---|---|
| Scenario Link | Supported | |
| Scenario Update | Supported | Temporary limitation: Reports scenarios as “updated” when the last change was a link add/remove |
| Synchronize Title | Supported | |
| Synchronize Steps | Supported | |
| Synchronize Tags | Supported | |
| Synchronize Steps: Data Tables | Supported | |
| Synchronize Steps: DocStrings | Supported | |
| Synchronize Steps: Scenario Outlines | Supported | |
| Synchronize Links | Supported | Except “parent link” |
| Synchronize Pull Request Links | Not available | No matching concept |
| Synchronize State | Planned for v2 | |
| Synchronize Area | Planned for v3+ | Matching Jira concepts are currently evaluated |
| Synchronize Iteration | Planned for v3+ | Matching Jira concepts are currently evaluated |
| Synchronize Automation | Planned for v3+ | Matching Jira concepts are currently evaluated |
| Synchronize Attachments | Planned for v2 | |
| Synchronize Local Test Case Source | Planned for v1.1 | The “customFieldUpdates” customization can be used for it |
| Format: useExpectedResult | Planned for v2 | For those TCM Solutions that have matching concept |
| Format: syncDataTableAsText | Not available | |
| Format: prefixBackgroundSteps | Supported | |
| Format: prefixTitle | Supported | |
| Format: showParameterListStep | Supported | Might be obsolete later, as the ADO limitation might not be applicable |
| Customization: fieldDefaults | Supported | Field ID or field name can be used |
| Customization: customFieldUpdates | Supported | Field ID or field name can be usedUse “{!ADF}” prefix to convert result to “Atlassian Document Format” |
| Customization: ignoreTestCaseSteps | Supported | |
| Customization: ignoreTestCaseTags | Supported | |
| Customization: ignoreNotSupportedLocalTags | Supported | |
| Customization: tagTextMapTransformation | Supported | |
| Customization: branchTag | Supported | |
| Customization: resetTestCaseState | Planned for v2 | Depends on State Synchronization |
| Customization: linkOnChange | Supported | Pull Request links are not supperted |
| Test Suite Remote Scope (Include synchronized Test Cases to a Test Suite) | Planned for v2 | For those TCM Solutions that have matching concept |
| Local Scopes (Excluding scenarios from synchronization) | Supported |
Features related to the “pull” command
| Feature | Support | Comment |
|---|---|---|
| Pulling Test Case changes to local scenarios | Supported | |
| Pulling new Test Cases as feature files | Planned for v2 | Depends on Remote Scope |
Features related to the “re-link” command
| Feature | Support | Comment |
|---|---|---|
| Re-link scenarios to new Test Cases | Planned for v3+ | Not supported, as it depends on “Copy Test Plan” ADO feature.Later can be considered in a way that the cloning will be performed by the command itself. |
Features related to the “publish-test-results” command
| Feature | Support | Comment |
|---|---|---|
| Publishing test result files | Planned for v3+ | The TCM Solutions handle this anyway usually.For some TCM Solution it can be implemented. |
| Support for Azure DevOps Test Plan / Test Suite based test execution | Not available | No such concept in Jira.The SpecFlow plugins are not needed. |
| Customization: multiSuitePublishTestResults | Not available | No generic Test Suite – Test Result association |
Installation
SpecSync for Jira can be installed in different ways depending on the project context.
For machines with .NET Core installed, the easiest way is to install SpecSync as a .NET tool, but you can also download native binaries for Windows, macOS or Linux. SpecSync can also be used as a Docker container.
For all installation options and detailed instructions, please check the Installation & Setup documentation page of SpecSync for Azure DevOps. The installation of SpecSync for Jira is similar, except:
- The NuGet package for .NET tool installation is: SpecSync.Jira
- The NuGet package for .NET Console App installation is: SpecSync.Jira.Console
- The executable used by the native binaries is called SpecSync4Jira (instead of SpecSync4AzureDevOps)
- The SpecSync for Jira Docker image is called specsolutions/specsync4jira
The native binaries can be downloaded from the Downloads page.
The official SpecSync Docker images are on Docker Hub.
Documentation
The SpecSync for Jira documentation can be downloaded. If you have any feedback, question or suggestion, please contact us.