Testing Complex Systems: Creating data and limiting scope
summary
Builds a concrete testing plan around a Purchase object that computes price from a Trip (200) plus a HotelStay (50 × 3 = 150 → 350), shows using factories and fixtures and stubs and mocks to keep unit tests fast, and recommends wrapping external services with small adapters and using VCR/WebMock for integration. Gives numbers: slow suites can balloon to 10–45 minutes, many tests break when ActiveRecord validations leak into setup, and shows how to limit scope.
AI-written summary · about
chapters (4)
- 0:00Start
- 2:54Limiting tests to a particular part of the code
- 4:45Driving modular design with tests
- 9:44Where to start?
