Take Control of your Integration Testing with Testcontainers
How easy is it to write and maintain integration tests when the system under test interacts with databases and message stores? It can be quite challenging. The lack of control over the setup of databases can increase the cost of integration testing. Sometimes we take the route of using an in-memory database instead of the one we employ in the production environment, making the tests less effective. With docker containers, you can simplify this to some extent by running the setup before invoking your tests. Imagine if you get to control the database environment right from within the test code. TestContainers bring in this convenience.
Outline/Structure of the Demonstration
- Demo 1: Using TestContainers for integration testing with real RDBMS (the one that you use in production) instead of using an in-memory database without sacrificing the flexibility.
- Demo 2: Using TestContainers for tests driving your code that relies upon S3 API with Loclstack.
- How Testcontainers simplify developing and maintaining integration tests
- A tool that you can start using right away
Developers, Testers, Leads, Architects
Prerequisites for Attendees
Experience of developing and maintaining integration tests or having worked with such a team