anchor.diff:  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.
  
positive.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
  
negative.code: 	}
  }
  ----
  
  === Running scenarios by tags
  
  You can filter tests by tag while running Serenity.
  
  ==== JUnit
  
  With JUnit tests, this can be achieved by providing a single tag or a comma separated list of tags from command line.
  If provided, only classes and/or methods with tags in this list will be executed.
  
  [source,xml]
  