anchor.diff:  ----
   mvn clean verify -Dtags="feature:Reporting, release:sprint-2"
   ----
  +
  +==== Cucumber
  +
  +With Cucumber framework, you need to use the cucumber.options system property for tests filtering.
  +
  +[source,xml]
  +----
  +mvn clean verify -Dcucumber.options="--tags release:sprint-2"
  +----
  +
  +==== JBehave
   
   In case JBehave is your framework of choice, you can filter tests by using +-Dmetafilter+ in your maven command, as follows:
   
  
positive.code: Scenario: Download account statement in SWIFT MT940 format
  ----
  <1> Cucumber doesn't need the Meta keyword
   
  This way, when executing the tests, you can configure one or more filters to run (or exclude from run) the tests with a particular tag.
   
  You can also use tags as a powerful reporting tool. Using +@tag+ or +@tags+, Serenity lets you define tags that will appear in the test reports:
   
  ----
  Executing an international payment
   
  Meta:
  @tag component: payment     //<1>
   
  Scenario: Executing an international payment as a standing order
  ----
  <1> Scenarios in this file all involve the Payment component
   
  These tags can take any 'name' and 'value' combination and so can be used to report on whatever aspects you need in the living documentation.
  
  TIP: In +@Step+ libraries you have access to both read and add tag values.
  
negative.code: ----
  @WithTagsValuesOf({"Reporting", "release:sprint-2"})
  ----
  
  In JBehave, you can add tags using the +Meta+ keyword:
  
  [source,java]
  ----
  Download account statements
  
  Meta:               //<1>
  @web @iexplorer     //<2>
  
  Scenario: Download account statement in SWIFT MT940 format
  ----
  <1> Tags need to be introduced by the Meta keyword
  <2> Tags start with @ and can be any text value
  
  With Cucumber, things are even simpler:
  
  [source,gherkin]
  ----
  Feature: Download account statements
  