Automated Tests: You Won't Find It in a Book!
summary
Shows a practical testing strategy using module-level tests that exercise each module’s public API rather than isolated single-method unit tests, replacing mocks with real implementations inside the module and using an in-memory test repository for persistence. Describes full integration tests that run the app against a real database and HTTP to assert saved records and REST responses, plus tradeoffs like duplicated test logic and brittleness from name changes.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:11Why test interest arose
- 3:40Simple unit test example
- 8:21Validation problems in tests
- 10:09Consequences of bad test practices
- 15:14Real implementations instead of mocks
- 18:46Modules and business APIs
- 24:04External module dependencies
- 25:29Testing with repositories
- 29:27Integration tests and their importance
- 33:47When to use unit vs integration tests
- 35:15Test naming conventions
- 36:18Building test objects
- 37:45Copying test cases
- 38:28Unit test pitfalls
- 39:12Tests and development speed
- 40:35Teams with vs without tests
- 41:18Summary
related talks
54mAutomated Tests: What Courses Won't Teach You
44mTesting the untestable - patterns and use cases analysis
57mAdvanced Testing Techniques: Tips from the trenches
29mTesting Applications - How to Do It Better?
01h 05mMicrotesting
52mBuilding Operable Software with TDD (but not the way you think)
47mTesting: How We Developers Do It on the Backend
26mTesting the Tricky Stuff