Linking Work Items using tags

SpecSync can synchronize the scenarios with Azure DevOps Test Cases. In order to be able to use these Test Cases in Azure DevOps, you might want to link them to other work items. For example, if the scenario is describing the behavior of the User Story #123, you make a link between the Test Case synchronized from the scenario and the story. This gives you a better traceability and allows you to create requirement- or query-based Test Suites in Azure DevOps. For example you can create a test suite that contains all Test Cases (scenarios) that are related to User Story #123.

Although you can establish these links manually, once SpecSync has created the test cases from the scenarios, it is an error-prone manual process. A better way to do this is to mark the relation of the scenarios to other work items via tags and let SpecSync create the necessary links between the work items.

For that you need to mark the scenarios with tags, like @story:123, and specify the tag prefix (in this case story) in the SpecSync configuration file. The links can be configured in the synchronization/links section of the configuration.

{
  ...
  "synchronization": {
    ...
    "links": [
      {
        "tagPrefix": "story"
      }
    ],
    ...
  },
  ...
}

This will synchronize the scenario with the Azure DevOps test case and establish a link between the test case and the user story #123 work item.

The links created by SpecSync are removed when the tag is removed from the scenario. The links created manually are never removed.

Links created by SpecSync v3.2 or earlier are not removed automatically.

SpecSync attempts to create and maintain work item tags during pull command. In order to choose the right tag for new Test Case link, it considers the specified target work item type (targetType setting). Therefore if you plan to use the pull command it is recommended to set the target type. See section Restrict linked work item to be of a specific type for details.

The work item tags

The work item tags should follow the pattern @prefix:N, where prefix is a label of your choice (e.g. story, bug or wi) and N is the ID of the related work item (e.g. 123).

The work item tag can be specified at scenario level or feature level. In the latter case, it behaves like you would have applied the tag for all individual scenarios. This can be useful if all scenarios in the feature file are related to a feature or a user story work item.

If the work item with the specified ID does not exist or the user who performs the synchronization does not have permission for it, SpecSync will display an error message for that particular scenario. If at least one scenario has failed to synchronize, the command line tool returns with the exit code 10.

In SpecSync v3.3 or earlier, tags, where N is not a valid number, are ignored.

Optionally you can add an additional label to the work item tags to help the readers to understand what the referred work item is about. The additional label has to be separated by the work item number with a colon (:) character, like @bug:456:argument_error_for_empty_input .

Using multiple tag prefixes

In order to distinguish between the different relations in the feature file, you can also use and synchronize multiple prefixes. E.g. you can tag a scenario with @story:123 and @bug:456 indicating that the scenario was related to the user story #123 and it fixes the bug #456.

In order to use multiple tag prefixes, you have to list multiple link type configurations within the synchronization/links section.

{
  ...
  "synchronization": {
    ...
    "links": [
      {
        "tagPrefix": "story"
      },
      {
        "tagPrefix": "bug"
      }
    ],
    ...
  },
  ...
}

SpecSync does not check the type of the referred work item. Specifying @bug:123 will also make the link between the user story #123 and the test case. Though you can establish different link types for the different prefixes.

Link types

SpecSync creates a "Tests" link type between the test cases and the other work items by default. If you want to establish another kind of relationship (e.g. Parent), you can specify the link type in the relationship setting. The specified relationship defines how the linked work item is related to the test case, e.g. specifying Parent means that the linked work item will be the parent of the test case work item.

{
  ...
  "synchronization": {
    ...
    "links": [
      {
        "tagPrefix": "story",
        "relationship": "Parent"
      }
    ],
    ...
  },
  ...
}

The link type name is case sensitive and might contain spaces.

For linking Pull Requests, the relationship setting is mandatory and has to be set to Pull Request.

Changing the link type will not trigger the re-synchronization of the scenario. If the scenario has been synchronized already, you have to to force synchronization using the --force command line option.

Restrict linked work item to be of a specific type

By default SpecSync will not verify the type of the linked work item: any type of work items can be used. You can enforce that a certain tag prefix can only be used for a specific work item type using the targetType setting.

When the "pull" command is used, SpecSync attempts to use the best tag prefix if there are multiple available by selecting the first with matching targetType or the first of the ones without targetType otherwise.

The following example allows using the @bug: prefix only for "Bug" work items.

{
  ...
  "synchronization": {
    ...
    "links": [
      {
        "tagPrefix": "bug",
        "targetType": "Bug"
      }
    ],
    ...
  },
  ...
}

Linking Pull Requests

Test Cases can also be linked to Pull Requests using tags. For that the relationship setting of the link specification must be set to Pull Request.

Linking GitHub Pull Requests

Test Cases can also be linked to GitHub Pull Requests using tags. For further details on that please check the How to link GitHub pull requests guide.

Limitations

• In SpecSync v3.3 or earlier: Link tags are not created when the Test Case changes retrieved with the pull command.

• In SpecSync v3.2 or earlier: Existing test case links are not removed automatically, even if you remove the tag from the scenario. They have to be removed manually.