Organising Gherkin features with @Tags
Updated: Mar 4, 2020
Tags are a very powerful tool within AssertThat to help you organise your features and manage test execution. This article provides options for how you can use and organise your tasks to get the greatest benefit.
Tags provide a great way to easily add metadata to your Example Specification. Tags can be used for a multitude of reasons to help organise your features and scenarios for example:
Group or link related Business functionality
Test Automation pack - criticals, smoke, full
Test Automation status
Manual or Automated
Feature toggle status
Branch or feature-branch name
The level of test implementation - unit, api, acceptance
It’s very simple to add tags to scenarios to cater for however you want to organise your features. This can present its own set of problems as too many tags can be challenging to organise. This is when you need to carefully plan, manage and document how you organise your tags. My preference for doing this is with mind maps, for example:
If you do get to the stage where you do need to update your tags, AssertThat provides the tools and capabilities to bulk update tags using Scenario Manager.
AssertThat’s plugin provides a number of additional tools to simplify how you can use tags:
Scenario Manager - in addition to being able to add tags to scenarios and features, scenario manager allows you to bulk update your scenarios. Simply filter for your scenarios using name, tag, mode or linked issues and select the scenarios for bulk updating.
Manual / Automated - scenarios mode has be set to either manual or automated when the scenarios is added. When the feature is downloaded either through Jira or to your automated framework through AssertThat’s integrations each scenario will have a tag set to either Manual or Automated.
3. Linked defects and issues - Defects can be linked to features in multiple places, for example in the Features tab, in the Jira issue and also when triaging sceanarios under Reporting. Tags will be automatically added to the sceanario with the Jira issue id.
4. Feature and Scenario tags - tags can be added at either scenario or feature level. This provides the flexibility to easily group all scenarios under a feature and common tag.
If you would like a free demo or trial then please get in contact with us at firstname.lastname@example.org or a Try it for free - AssertThat BDD & Cucumber for Jira