Test Containers: Where Every Test Starts Fresh
summary
Claims that Testcontainers removes flaky, shared-state integration tests by spinning disposable Docker databases that mirror production and auto start and stop for each run, demonstrated with Spring Boot + PostgreSQL code that saves a user into a fresh DB and tears it down, showing tests become reproducible on Java Python and .NET CI runners. Addresses timing and data management problems and cites a real-world faulty deployment that hit 8.5 million devices and cost an estimated $500 million.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:29Software development lifecycle
- 3:13Testing in development
- 5:22Cost of integration test failures
- 7:11Integration test challenges
- 9:16What are Testcontainers
- 10:23How Testcontainers work
- 12:54Benefits of isolated tests
- 13:34Demo with Spring Boot
- 16:47Configuration best practices
- 18:16Cleanup and logging
- 19:01Versioning and images
- 20:05Conclusion and Q&A
related talks
53mTestcontainers: a year-in-review
45mTestcontainers - a Year-in-review
47mIntegration Tests: testcontainers to the Rescue
15mTestcontainers: Simplify Your Integration Tests and Development
01h 06mTestcontainers best practices.
51mTestContainers: Integration Testing Without the Hassle
46mTestcontainers - The past, the present and the future
26mRemoving Complexity from Integration Tests Using Testcontainers