anchor.diff:  	}
   }
   ----
  - 
  +
   === Running scenarios by tags
   
  -You can filter tests by tag while running Serenity. With JUnit tests, this can be achieved by providing a single tag or a comma separated list of tags from command line.
  +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]
  
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: In real-world projects, scenarios can become quite numerous, and it's important to keep them well organized. You may also need to be able to identify and group scenarios in different ways;
  for example, you might want to distinguish UI-related scenarios from batch-processing scenarios, or identify the regression scenarios only.
  
  Tags are also a great way to help organize test execution. For example, you might want to flag all of the web services tests, or mark certain tests to run against Internet Explorer browser only.
  
  === Annotating scenarios with tags
  
  Tags are added to JUnit tests using +WithTag+ annotation. The following will add a tag of type _epic_ with name _Audit_:
  