SOLID and TDD, Sitting in a
summary
Claims that TDD alone yields good design are false and demonstrates with a Rails messaging example: a bulky Notifier gets refactored into small notification channel objects, tests switch from long integrated specs to focused unit tests, and dependency injection plus stubbing ActionMailer and using FactoryGirl produces faster clear tests. The talk shows the code change, the tests shorten, concretions migrate to cohesive classes, and the rebuilt system works and is far easier to change.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:06SOLID & TDD
- 3:37Interface Segregation
- 4:26Depending on a Concretion
- 4:40Depending on an Abstraction
- 5:08Dependency Inversion Principle
- 5:32Open/Closed Principle
- 7:23Liskov Substitution Principle
- 8:26Single Responsibility Principle
- 14:07Responsibilities Described
- 14:47Strained Language
- 18:36Guidelines for Pain- Free Testing
- 28:36Gold Sponsor
