Test-Driven: from Zero to Hero
summary
Claims that most enterprise codebases arrive with zero test code and that introducing tests is practical using Java 17 with Maven + JUnit 5. Demonstrates unit patterns (return-first, AAA), uses McCabe to estimate needed cases, measures coverage with JaCoCo, and shows integration tests running an embedded Grizzly server and a Postgres instance via Testcontainers (Docker required). Shows builds work end-to-end but integration tests are noticeably slow; recommends start bottom-up and keep tests compact.
AI-written summary · about
chapters (21)
- 0:00Introduction and setup
- 3:38Why software projects fail
- 5:02Starting with test automation
- 6:26Test-driven development basics
- 7:10Recommended testing tools
- 8:12Configuring Maven for tests
- 9:17Writing testable code
- 12:27Unit test structure and AAA principle
- 16:43Test case complexity and coverage
- 19:12Measuring test coverage with Jacoco
- 22:26Benefits of test-driven development
- 23:07Limitations of tests
- 24:34Integration tests overview
- 25:40Configuring Maven for integration tests
- 27:48Testing microservices with embedded servers
- 31:44Live demo of integration testing
- 35:40Database setup in tests
- 37:28Test containers introduction
- 41:04Implementing test-driven development
- 43:56Summary and key takeaways
- 44:40Q&A session
related talks
42mTest-Driven Repair
02h 43mSpring Boot testing: Zero to Hero
01h 09mTDD Workshop, tests are your best ally
38mSetting up data driven tests with Java tools
40mIntegration Testing from the Trenches - Rebooted
41mTesting done right: From bugs to brilliance
42mEffective Developer Testing: taking it to the next level
48mEffective Unit Testing