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: and a corresponding integration test
  
  ----
  grails> create-integration-test BookIntSpec
  ----
  
  Now write a simple integration test which will verify, that persisting a `Book` works. At which point in the test
  lifecycle would you set the configuration values?
  
  ****
  You might need additional runtime dependencies! You'll also notice scary error messages in red when the database container
  is starting. These do occur because TestContainers will try to connect to the starting database using the PostgreSQL JDBC
  driver in order to determine if the database is ready to interact with. These error logs will not appear anymore in the
  next TestContainers release.
  ****
  
  
  == Interact with an external HTTP-Server
  
negative.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.
  
  [TIP]
  ====
  You can also head over to http://start.grails.org/[Grails Application Forge] and download a ready to use
  Grails project and use the Gradle-Wrapper and circumvent install Gradle altogether.
  ====
  
  === TestContainers Quickstart
  
  