anchor.diff:  image::subset-of-tests-for-filtering.png[]
   
   
  -It is easy to filter some of them with starting typing their name in filter field:
  +It is easy to filter some of them with starting typing its name in filter field:
   [[filtered-tests-for-filtering]]
   .Serenity BDD report example with applied filter
   image::filtered-tests-for-filtering.png[]
  
positive.code: 
  ==== Filtering in Serenity Reports
  
  For better user experience in Serenity BDD aggregated reports available filtering feature. It makes much easy to find particular subset of tests by names if you have a lot of test, features, etc.:
  
  For example you have next tests:
  [[subset-of-tests-for-filtering]]
  
negative.code: 
  === Detailed description of aggregation reports
  
  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:
  
  