How Fixing a Broken Window Cut Down Our Build Time by 50%

Discover how addressing a "broken window" in a Spring Boot integration test setup led to a 50% reduction in build time in this conference talk from Spring I/O 2022. Explore the broken windows theory applied to codebases, where one suboptimal pattern can lead to widespread issues. Learn about the pitfalls of using @DirtiesContext on an abstract test class and its impact on Spring TestContext reusability. Gain insights into best practices and antipatterns for testing Spring Boot applications, including context caching, data management, and setup strategies. Follow the speaker's journey from a 25-minute build time to just 12 minutes, and understand the importance of maintaining clean architecture principles in test setups. Acquire valuable knowledge on optimizing Spring Boot test performance and improving overall team satisfaction through efficient feedback cycles.

Intro
How Fixing a Broken Window Cut Down Our Build Time by 50%
How It Started
The Broken Windows Theory
It Does Not Always have to Be a Window
Impact of Fixing the Broken Window
Goals for This Talk
Spring TestContext Framework: Context Caching
Spring TestContext Framework Context Caching
Context Caching and Reusability Red Flags
Context Caching Indicators
Message Thefts
Pitfall #2: Data Overflow
Remote Connections
Pitfalls: Setup Variety
The Result
Testing Spring Boot Applications Masterclass
Stratospheric - From Zero to Production with Spring Boot and AWS
Conclusion