anchor.diff:  }
   
   dependencies {
  -    compile 'com.github.testcontainers:testcontainers-spock:87299c10e8'
  +    testCompile 'com.github.testcontainers:testcontainers-spock:87299c10e8'
   }
   ----
   
   ==== @Testcontainers class-annotation
   Specifying the @Testcontainers annotation will instruct Spock to start and stop all
  -testcontainers accordingly. This annotation can be mixed with Spock's @Shared annotation to indicate, that containers shouldn't be restarted between tests.
  +TestContainers accordingly. This annotation can be mixed with Spock's @Shared annotation to indicate, that containers shouldn't be restarted between tests.
   
   [source, groovy]
   ----
  
positive.code: testCompile group: 'org.testcontainers', name: 'postgresql', version: '1.2.1'
  ----
  
  
  === Special JDBC URL
  
  TestContainers provides a special injection point for using a database container in your integration tests.
  If TestContainers is on the classpath, it's sufficient to use a special JDBC url and TestContainers
  will automatically spin up a fresh database container once the application starts. All you have to do
  is inserting a `tc:` after `jdbc:` part of the JDBC URL:
  
  ----
  jdbc:tc:postgresql://hostname/databasename
  ----
  
  
  === Using System Properties
  asd
  
  
  ****
  Could you inject these configuration values in a way that's more idiomatic to Grails?
  Spring-Boot allows the usage of `ApplicationContextInitializer`, but I wasn't able to get this working
  in conjunction with
  ****
  
  === Sharing Database between tests
  
  
  
  === Exercises
  
  
  
  
  == Interact with a FTP-Server
  
  
  == Functional testing using Geb and Selenium
  
  
  == Acknowledgements
  
  
negative.code: we'll use in this workshop.
  
  Since the most recent snapshot versions are available at https://jitpack.io/[jitpack.io], you can
  include the dependency in your `build.gradle` file like this:
  
  [source, groovy]
  ----
  