Integration Testing from the Trenches - Rebooted
summary
Argues for concrete practices: run fast unit-like tests on every commit and run slow integration suites at intervals, name tests so Maven Surefire handles fast ones and Maven Failsafe handles slow ones, prefer H2 in-memory for fast feedback and testcontainers or a real DB for periodic verification, inject time and filesystem dependencies (use Path not java.io.File), design configuration as testable fragments, and set pool size to one in tests to catch connection leaks early.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Speaker intro
- 3:15Integration testing defined
- 6:48System under test
- 13:08Slow fragile tests
- 18:05Fast vs slow tests
- 21:12Decoupling infra
- 26:56Framework configs
- 31:52Key takeaways
- 34:23Q&A
related talks
58mIntegration Testing from the Trenches
01h 20mIntegration Testing from the Trenches
57mAdvanced Testing Techniques: Tips from the trenches
44mTesting: Integration Tests - The good, bad and ugly
46mTesting the untestable - patterns and use cases analysis
48mTesting is Confidence - A Developer's Perspective
42mUse testing to Develop Better Software Faster
37mUnderstanding the successes and the pain points of different testing strategies