anchor.diff:  -------------------------------------------------------------------------------
   
   Our experience demonstrated that we never need to use complex selector. If you write tests first, the component tested carries
  -a semantic and this semantic must be reflected in the code by an ID or a role (data-role attribute is commonly used in web development).
  +a semantic and this semantic must be reflected in the code by an ID a role (role attribute is commonly used in web development) or
  +better a specific tag (with Angular Directive or Web Components)
   
   Once the component is selected, it must be *TYPED* throw the *"as"* keyword.
   
  
positive.code: a page with two radio buttons to select the gender (male or female), the test can be expressed like this :
  
  -------------------------------------------------------------------------------
  assert that the maleRadio is unchecked
  and it has label "Male"
  
  assert that the femaleRadio is unchecked
  and it has label "Female"
  
  check the maleRadio
  assert that the maleRadio is checked
  assert that the femaleRadio is unchecked
  
  check the femaleRadio
  assert that the femaleRadio checked
  assert that the maleRadio is unchecked
  -------------------------------------------------------------------------------
  
  The Testatoo syntax to express this specification is :
  
negative.code: <dependency>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-java</artifactId>
      <version>2.42.2</version>
      <scope>test</scope>
  </dependency>
  -------------------------------------------------------------------------------
  