Session
Top 5 Spring Boot Testing Mistakes Developers Trap Into
Your Spring Boot tests are passing, but can you trust them? In recent years, most of your tests aren't written by you - an AI wrote them while you reviewed the diff. That makes testing more important than ever, yet for many teams it remains a neglected afterthought.
This session reveals five mistakes that silently undermine your test suite's reliability and your confidence in deployments. We'll tackle the tough questions: How can 100% coverage still miss critical bugs? Why is your test suite so slow? Why does everything pass on H2 and fail in production?
You'll see real tests that look correct but hide serious flaws: @SpringBootTest as the golden hammer, the hidden context tax of careless @MockBean usage, in-memory databases that fake production parity, @Transactional rollbacks that make commits vanish, and green tests that can never fail. Each pitfall comes with practical fixes: picking the right test slice, reusing the application context, testing against real infrastructure with Testcontainers, and challenging your coverage with mutation testing.
You'll learn to judge tests, whether written by a human or an AI, and ship with certainty instead of hope. Perfect for developers burned by production issues despite "comprehensive" test suites.
Joyful testing awaits!
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top