Unit tests and TDD does NOT have to be boring
summary
Shows how writing HTTP test client tests for a bank-account API (GET list, POST create, PATCH update) forces specific assertions: exact JSON fields, HTTP status codes, and error messages. Uses fake-data generators to post accounts, verifies database values and that UI sees only last four digits masking. Tests reveal and help fix integration bugs quickly, let front-end work independently, and yield reproducible one-command debugging and clearer 70–80% coverage targets.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:44Why write unit tests
- 1:24Code quality
- 4:24Testdriven development
- 5:50Project example
- 8:29Python API
- 10:30Unit tests
- 13:14Writing Python code
- 14:09The results
- 16:48TDD benefits
- 17:11Test cases
- 18:17Debugging
- 18:48Helpful bug
- 19:54Code coverage
related talks
56mBuilding Operable Software with TDD (but not the way you think)
52mBuilding Operable Software with TDD (but not the way you think)
01h 05mMicrotesting
58mTDD for database related code, how is it possible?
54mAutomated Tests: What Courses Won't Teach You
52mBuilding Operable Software with TDD (but not the way you think)
01h 01mTDD Revisited
46mHow John Started to Like TDD (Instead of Hating It)