anchor.diff:  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
  +expect the maleRadio is unchecked
   and it has label "Male"
   
  -assert that the femaleRadio is unchecked
  +expect the femaleRadio is unchecked
   and it has label "Female"
   
   check the maleRadio
  -assert that the maleRadio is checked
  -assert that the femaleRadio is unchecked
  +expect the maleRadio is checked
  +expect the femaleRadio is unchecked
   
   check the femaleRadio
  -assert that the femaleRadio checked
  -assert that the maleRadio is unchecked
  +expect the femaleRadio checked
  +expect the maleRadio is unchecked
   -------------------------------------------------------------------------------
   
   The Testatoo syntax to express this specification is :
  
positive.code: -------------------------------------------------------------------------------
  
  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).
  
  Once the component is selected, it must be *TYPED* throw the *"as"* keyword.
  
  
negative.code: <dependency>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-java</artifactId>
      <version>2.42.2</version>
      <scope>test</scope>
  </dependency>
  -------------------------------------------------------------------------------
  