anchor.diff:  [source,scala,subs="attributes"]
   ----
   "mvn:de.tototec:de.tobiasroeser.lambdatest:{lambdatestversion}" ~
  -  "mvn:org.testng:testng:6.8.8"
  +  "mvn:org.testng:testng:{testngversion}"
   ----
   
   
  
positive.code: 
  [source,java]
  ----
  package org.example;
  
  import static de.tobiasroeser.lambdatest.Expect.expectEquals;
  
  import de.tobiasroeser.lambdatest.testng.FreeSpec;
  
  class SimpleTest extends FreeSpec {{
  
    test("1 + 1 = 2", () -> {
      expectEquals(1 + 1, 2);
  
negative.code: 
  ----
  
  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:
  
  * Nice output of differences of various collections
  * non-fail-fast behaviour to collect as much assertion errors as possible in one test run
  