anchor.diff:  ---
   Feature:Definition
   		Story: Look for definition
  -			Scenario: Looking for definition
  +			Scenario (or Test, or Acceptance Criteria): Looking for definition
                   examples: 3
                   steps: 3
   			Scenario: Looking for definition with incorrect symbols: ignored
  
positive.code: 			  	steps: 3
  ---
  
  After running all test (doesn't matter if you use jBehave, Cucumber or JUnit) you will receive aggregation report, that will look similar with structure of tests:
  
  [[basic-concepts-detailed-test-count]]
  .Serenity BDD report for test structure on tab Test Count
  image::basic-concepts-detailed-test-count.png[]
  
  
  Report contains next tabs:
  
  *Overall Test Results*:: contains test results of all executed scenarios, general info about provided features/components stories in this test. Also statistics of passing/ignoring/skipping/failing based on amount of tests and examples under them.
  
  *Requirements*::
  
  
  
  
negative.code: 
  === 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.
  
  