anchor.diff:  
   === Detailed description of aggregation reports
   
  -Serenity BDD aggregation report can be organised with using features, stories, steps, scenarios/tests. When you using different framework with Serenity BDD it is possible that same things will have different names - for example `examples` in jBehave/Cucumber have almost same minion as `Test Data` during using Junit, or `scenario` in jBehave/Cucumber and `test` in JUnit. Also *Test* - it synonym of *Acceptance Criteria*. We will use some short example for this chapter to describe serenity bdd report, how create and organise all test process you can find in next chapters.
  -
  -Our example will contain 2 feature, and some amount stories. Each story can contains one or more scenario, each scenario can contains one or moro step ond use some amount of examples. If you don't use any examples - it the same as you use 1 example.
  +Serenity BDD aggregation report can be organised by using features, stories, steps, scenarios/tests. When you use different frameworks with Serenity BDD it is possible that the same things will have different definitions. For instance, `examples` in JBehave/Cucumber has almost same meaning as `Test Data` in Junit, or `scenario` in JBehave/Cucumber is the same as `test` in JUnit. Also *Test* is a synonym of *Acceptance Criteria*. Here is introduced some short example in order to describe Serenity BDD report. The way of creating and organising the whole test process you can find in next chapters.
  +
  +Our example contains 2 features with a few stories. Each story can contain one or more scenarios, each scenario consists of one or more steps and some examples. The default amount of examples is 1.
   
   Sample:
   
  
positive.code: ----
  
  
  *ignored* = 2 - amount of all scenarios are marked to be ignored. To get this number Serenity counts scenarios are marked to be ignored. In our case there is 2 such scenario.
  
  *skipped* = 1 - amount of all scenarios are marked to be skipped. To get this number Serenity counts scenarios are marked to be skipped. In our case there is 1 such scenario.
  
  *with errors* = 5 - amount of all scenarios what throw some unexpected exception during execution. To get this number Serenity count scenarios or examples for those scenarios if provided. In our case there is 1 such scenario with 5 examples.
  
  *failed* = 2 - amount of all scenarios what fail. To get this number Serenity counts scenarios or counts examples for those scenarios if provided. In our case there is 1 such scenario with 2 examples.
  
  *pending* = 1 - amount of all scenarios are marked to be pending. To get this number Serenity counts scenarios or examples for those scenarios if provided. In our case there is 1 such scenario without examples.
  
  *passes* = 4 - amount of passed scenarios. To get this number Serenity counts scenarios or examples for those scenarios if provided. In our case there are 2 such scenario: one without examples, and second with 3 examples.
  
  *rows of test data* = 10 - amount of all examples from scenarios witch are used in this report, including skipped scenarios and without ignored scenarios. To get this number Serenity counts examples for those scenarios if provided. In our case there are 3 such scenario: with 2, 3 and 5 examples.
  
  *tests in all* = 15 - sum of "ignored", "skipped", "with errors", "failed", "pending", "passes" values
  
  
negative.code: 
  ==== Filtering in Serenity Reports
  
  To provide a better user experience, there is available a filtering feature in Serenity BDD aggregated reports. It makes much easier to find particular subset of tests by names, features, etc.
  
  For example you have next tests:
  [[subset-of-tests-for-filtering]]
  