anchor.diff:  
   ----
   
  -You should write your test cases so that they don't need to be executed in order. LambdaTest is able to run tests in parallel, if you enable it explicitly with `FreeSpec.setRunInParallel(true)`.
  -
  -You can disable fail fast behaviour for assertion/expectations with `FreeSpec.setExpectFailFast(false)`. Than, the first failing assertion error will non abort the test but the test is optimistically continued. Further failing assertion errors are collected and reported at the end of the test.
  +You should write your test cases so that they don't need to be executed in order.
  +LambdaTest is able to run tests in parallel, if you enable it explicitly with `FreeSpec.setRunInParallel(true)`.
  +
  +You can disable fail fast behaviour for assertion/expectations with `FreeSpec.setExpectFailFast(false)`.
  +Then, the first failing assertion error will not abort the test but the test is optimistically continued. Further failing assertion errors are collected and reported at the end of the test.
   
   == Writing assertions with `Expect`
   
   As an alternative to the assertion methods provides by other unit testing framework, you can instead use `Expect` and it's `expectXXX`-methods.
   
  -Why should you, you ask` Here are some reasons:
  +Why should you, you ask? Here are some reasons:
   
   * Nice output of differences of various collections
   * non-fail-fast behaviour to collect as much assertion errors as possible in one test run
  
positive.code: [source,scala,subs="attributes"]
  ----
  "mvn:de.tototec:de.tobiasroeser.lambdatest:{lambdatestversion}" ~
    "mvn:org.testng:testng:6.8.8"
  ----
  
  
  
negative.code: [source,scala,subs="attributes"]
  ----
  "mvn:de.tototoec:de.tobiasroeser.lambdatest:{lambdatestversion};classifier=java7" ~
    "mvn:org.testng:testng:{testngversion}"
  ----
  
  
  