anchor.diff:  
   ==== 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.:
  +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]]
  
positive.code: 
  ===== Sub-Tab Test Count
  
  As you can see on <<basic-concepts-detailed-test-count>>, it contains next elements: Pie Chart, Test Result Summary table, Related Tags table, Tests table.
  
  *Test Result Summary*:
  This table contains more detailed statistics than short summary above.
  
  Row *Automated* contains automated tests.
  
  - *Ignored* - count of automated tests 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.
  
  - *Percent of ignored tests* - percentage of *Ignored* tests to *tests in all*. In our case there are 2 such scenario, and it is 13% from 15.
  
  - *Pending* - 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.
  
  - *Percent of pending tests* - percentage of *Pending* tests to *tests in all*. In our case there is 1 such scenario, and it is 7% from 15.
  
  - *Fail* - amount of all scenarios what fail plus scenarios with errors. To get this number Serenity counts scenarios or counts examples for those scenarios if provided. In our case there is 1 fail scenario with 2 examples and 1 error scenario with 5 examples - 7 at all.
  
  - *Percent of fail tests* - percentage of *Fail* tests to *tests in all*. In our case there are 7 scenarios/examples and it is 47% from 15.
  
  - *Pass* - 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 - 4 at all.
  
  - *Percent of passed tests* - percentage of *Pass* tests to *tests in all*. In our case there are 4 scenarios/examples and it is 27% from 15.
  
  - *Total* - equal to *tests in all*
  
  Row *Manual* contains manual tests, to do test manual you should use @Manual annotation, idea the same as for Automated row. Generally it is possible mark as manual scenarios (@manual on scenario level) or all scenario in story (@manual on Story level). The @Manual annotation is not designed to be defined for an individual step within a test, but only for the whole test.
  
  Row *Total* should contains summary for each column.
  
  
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:
  
  