anchor.diff:  }
   ----
   
  -
  -****
  +[NOTE]
  +====
   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 Grails' `@Integration` AST transformation. I'd be happy to receive suggestions from the Grails
   gurus ;)
  -****
  +====
   
   === Exercise
   
  
positive.code: 
  You can import the generated project into Intellij using `File -> New -> Project from existing sources...` and select the
  `build.gradle` file inside the directory.
  
  === TestContainers Quickstart
  
  
negative.code: testCompile group: 'org.testcontainers', name: 'postgresql', version: '1.2.1'
  ----
  
  === TestContainers JDBC-URL
  
  As long as you have TestContainers and the appropriate JDBC driver on your classpath, you can simply modify regular JDBC
  connection URLs to get a fresh containerized instance of the database each time your application starts up (meaning
  on initialization of the JDBC connection pool).
  
  [CAUTION]
  =====
  Attention when using Spring-Boot (or Grails for that matter). In this case you have to specify the following JDBC driver:
  
  `spring.datasource.driver-class-name=org.testcontainers.jdbc.ContainerDatabaseDriver`
  
  which would translate to something like this for Grails:
  
  ----
  dataSource:
    dbCreate: create
    url: jdbc:tc:postgresql://hostname/databasename
    driverClassName: org.testcontainers.jdbc.ContainerDatabaseDriver
  ----
  
  =====
  
  ==== MySQL
  
  ----
  jdbc:tc:mysql://somehostname:someport/databasename
  ----
  
  ----
  jdbc:tc:mysql:5.6.23://somehostname:someport/databasename
  ----
  
  ==== PostgreSQL
  
  ----
  jdbc:tc:postgresql://hostname/databasename
  ----
  
  
  === Configure SUT at runtime using System Properties
  
  We want our tests to be as portable as possible and so one shouldn't make assumptions regarding the environment they are
  