Testcontainers co-maintainer and Testcontainers-Spock author, passionate about OSS, containers and Linux. Oracle Groundbreaker Ambassador. Software Crafter and testing fan. Fell in love with TDD because of Spock. Believes in Extreme Programming as one of the best Agile methodologies. Likes to write MATLAB and Python programs to support his wife in performing behavioural science experiments with pigeons. Plays the electric guitar and is a musician in his second life.
After many years working in the industry as an engineer, Kevin is now doing his PhD in computer science in the field of distributed systems engineering and is leading the Blockchain Lab at the Institute for Internet Security in Gelsenkirchen, Germany at the Westphalian University of Applied Sciences.
Unit testing is fine, but without proper integration testing, especially if you work with external resources like databases and other services, you might not know how your application will actually behave once it has been deployed to the real production environment.
Before Docker, configuring the environment for integration testing was painful – people were using fake database implementations, mocking servers, usually it was not cross-platform as well. However, thanks to Docker, now we can quickly prepare the environment for our tests.
In this workshop, I would like to show how you can use Testcontainers ( https://github.com/testcontainers/testcontainers-j...
) – a popular Java testing library that harnesses Docker to easily, reliably, spin up test dependencies. We will use it with a Spring Boot microservice and test against real PostgreSQL and Redis data stores, we'll isolate it from other microservices, then start Selenium browsers in Docker and test our application, and all with the same library!
Come and learn why Apache, Spring, ZeroTurnaround, JetBrains, Playtika, Zipkin and others already decided to use Testcontainers for their integration testing