Getting started using SpecFlow

This chapter goes through the setup and the synchronization steps for SpecFlow projects. For non-SpecFlow projects, like Cucumber, please check page Getting started using Cucumber.

SpecSync is a synchronization tool that can be invoked from the command line. This guide shows you step-by-step how the synchronization tool can be configured.

Preparation

For setting up SpecSync for Jira, you need a SpecFlow project and a Jira project. For the supported Jira versions, please check the Compatibility list.

In our guide, we will use a calculator example (MyCalculator) that uses SpecFlow v2.3 with MsTest. The SpecFlow project is called MyCalculator.Specs. The sample project can be downloaded from GitHub.

For a synchronization target we use a Jira project: https://specsyncdemo.atlassian.net/MyCalculator.

Installation

There are multiple installation options you can choose from depending on your operating system and the development platform (see details at Installation & Setup page). In this guide we configure SpecSync for a .NET Core 3.1 project and will install SpecSync as a local .NET Core Tool.

If SpecSync is the first local .NET Core tool in your project, you have to initialize the .NET Core tool configuration first. For that open a command line prompt and go to your solution folder.

dotnet new tool-manifest

Once the configuration is initialized, you can install SpecSync. Change the current directory to your SpecFlow project folder (MyCalculator.Specs in our case) and install the SpecSync package:

cd MyCalculator.Specs
dotnet tool install SpecSync.Jira 

If the installation was successful, you can invoke SpecSync using the dotnet specsync command. For example the following command displays the version of SpecSync.

dotnet specsync version

You can find more information about this installation option in the Install as .NET Core tool page.

Initialize configuration

Initialize the SpecSync configuration in your local repository root by invoking the SpecSync init command. This command will create a SpecSync configuration file specsync.json.

dotnet specsync init

The init command will ask you for your Jira project URL and the authentication credentials. Alternatively you can manually create the configuration based on an empty configuration file downloadable from http://schemas.specsolutions.eu/specsync-jira-empty.json.

Review configuration

The init command configured the connection details to your Jira project. This is enough to start the first synchronization. But before we move on with that, let's review the created configuration file.

Open the specsync.json file in Visual Studio or another IDE from your project folder. The file should contain configuration settings similar to the ones below.

specsync.json

{
  "$schema": "http://schemas.specsolutions.eu/specsync4jira-config-latest.json",

  // See configuration options and samples at http://speclink.me/specsyncconfig.

  "remote": {
    "serverUrl": "https://specsyncdemo.atlassian.net/",
    "project": "MyCalculator",
    "user": "52yny........................................ycsetda"
  }
}

First synchronization

1. Make sure your project compiles.

2. We recommend starting from a state where

   • all tests pass,

   • the modified files are checked in to source control.

3. Open a command line prompt and navigate to the SpecFlow project folder (MyCalculator.Specs)

4. Invoke SpecSync push command:

   dotnet specsync push

5. If you haven't specified any credentials in the configuration file, an authentication dialog will popup, where you have to specify your credentials for accessing the Jira project.

As a result, the scenarios from the project will be linked to newly created Jira test cases, and you will see a result like this.

Result of the first synchronization

Scenarios are synchronized to normal, Scenario Outlines to parametrized test cases.

Check Test Case in Jira

1. Find one of the created test case in Jira.

There are a couple of things you can note here.

• The name of the scenario has been synchronized as the title of the test case. (The "Scenario:" prefix can be omitted by changing the synchronization format configurations.)

• The tags of the scenario have been synchronized as test case tags (labels).

• The steps of the scenario have been synchronized to the test case depending on the used Jira TCM solution. In most of the integrations it is synchronized as Gherkin text.

Verify feature file and commit changes

1. Open one of the feature files from the SpecFlow project in Visual Studio. SpecSync modified the file and added a few tags.

2. Each scenario and scenario outline has been tagged with a @tc:... tag making the link between the scenario and the created test case.

@tc:P01-T1234
@important
Scenario: Add two positive numbers

The feature files are changed only when synchronizing new scenarios (linking). To avoid file changes (e.g. when running the synchronization from a build server) the --disableLocalChanges command line switch can be used. See Synchronizing test cases from build for details.

Verify if the project still compiles and the tests pass (they should, since we have only added tags), and commit (check-in) your changes.

Synchronize an update

Now let's make a change in one of the scenarios and synchronize the changes to the related test case.

1. Update the title and the steps of the scenario, for example change the scenario Add two positive numbers to Multiply two positive numbers, change add to multiply in the When step and update the expected result to 377:

   @tc:P01-T1234
   Scenario: Multiply two positive numbers
     Given I have entered the following numbers
        | number |
        | 29     |
        | 13     |
     When I choose multiply
     Then the result should be 377

2. Make sure it still compiles and the test passes.

3. Run the synchronization again:

   dotnet specsync push

The result shows that the test case for the scenario has been updated, but the other test cases have remained unchanged (up-to-date).

Result of synchronizing an update

1. Refresh the test case in your browser to see the changed title and steps.

   

   Updated test case in Jira

Publishing test results (optional)

So far we have shown how to keep the Jira Test Cases in sync with the scenarios in the feature files. This provides you easily accessible documentation and traceability. The synchronized Test Cases can also be executed as manual tests from Jira.

To turn the Test Cases into a living documentation, you can also publish test results of the scenarios connected to the Test Cases.

The easiest way to do this is to execute the SpecFlow scenarios as you would do normally and use the publish-test-results command of SpecSync to publish these results to Jira.

First let's execute the tests. In this example we use a fixed test result file name testresult.trx.

dotnet test --logger trx;logfilename=testresult.trx

When the test execution has been finished, the test result file is updated. The default location of the file is the TestResults folder.

Now lets publish these results using the publish-test-results command of SpecSync.

dotnet specsync publish-test-results --testResultFile TestResults\testresult.trx

The command analyses the test result file and connects the results with the scenarios to be able to associate them to Test Cases.