Introduction to TestContainers for Integration Testing
- 2. What is Testcontainers? ● Testcontainers is a library that can manage container life cycle during tests ● It provides lightweight, throwaway instances of common databases, cloud services, SFTP servers, message queues or anything else that can run in a Docker container
- 4. When do we use Testcontainers? When we want to test the interaction between the application with other external components in a production-like environment: ● Data access layer integration tests: MySQL, PostgreSQL or Oracle database ○ For example, regression tests when we move to another database ● Application Integration Test: SFTP, message queues ● Cloud Service Integration Test: AWS stacks, Azure, GCP...
- 5. Advantages ● Easy to set up ● Containers Life Cycle auto-management ○ Wait for containers to start before executing the tests ● Clean up after tests done ○ Shut down containers after each test or reuse same containers for all tests ● No need to manage port ○ Each container is assigned a free port and can be programmatically retrieved ● No need to stop containers if tests are stopped abruptly ○ There is a heartbeat container that will kill running containers after JVM shutdowns
- 7. Advantages cont. ● Can work with any container image on Docker Hub or custom images ● Work with JUnit 5 and Spring Boot ● Work with Spock ● Work with Python, NodeJs and more is coming ○ https://github.com/testcontainers
- 8. Drawbacks ● Docker required ● Slower than Unit Tests
- 9. Questions
- 10. Demo
- 11. Conclusion TestContainers is a good option to improve the quality of the applications and gives us some confidence that the application will work and interact correctly with different components in production-like environment.
Editor's Notes
- #5: https://github.com/localstack/localstack https://www.testcontainers.org/modules/localstack/