Automated Tests: What Courses Won't Teach You
summary
Advocates for module-level unit tests that use real implementations instead of heavy mocking, demonstrated with a Spring-based rating API (age×2) and an in-memory test repository and controller. Shows a one-line switch to inject a real calculator to avoid brittle mock setups, and presents JUnit-style module/unit tests alongside full integration tests that boot the app and assert HTTP 200, JSON payload and a DB row; code examples are on GitHub. Emphasizes using a module API as a facade and Given‑When‑Then naming.
AI-written summary · about
chapters (15)
- 0:00Automated tests intro
- 4:54Simple rating system
- 7:06Unit tests pitfalls
- 11:27Fixture problems fixes
- 15:40Business modules benefits
- 22:53API dependency testing
- 26:26External dependencies integration
- 31:28Integration tests role
- 36:47Contract process testing
- 41:44Testing vs dev speed
- 43:53Q&A: Complex cases
- 46:29Q&A: External API tests
- 47:10Q&A: Scaling suites
- 51:53Q&A: Legacy projects
- 52:13Q&A: Test narratives
related talks
42mAutomated Tests: You Won't Find It in a Book!
01h 46mHow Java developers should test their applications (RU)
41mTesting done right: From bugs to brilliance
01h 05mMicrotesting
41mAm I Testing the Right Way? - Two Unit-Testing Approaches Explained!
44mTesting the untestable - patterns and use cases analysis
46mThe Good, The Bad, and The Stubbed: A Java Unit Testing Adventure
02h 46mThe Joy of Testing