Better code through boring(er) tests
summary
Tests get painful for three concrete reasons: testing private methods (fix by making the method public, extracting a class, or adding test-friendly introspection), duplicated tests across clients/donors (fix by extracting a query class or repository so tests and app code co-evolve), and “inventing the universe” setup (fix by moving important setup into constructors or application-level factory methods, or by using WebMock for external services). Uses minitest/rspec, FactoryGirl, ActiveRecord, mocks/partial mocks; tradeoffs are realism versus focused, fast tests and CI speed.
AI-written summary · about
chapters (15)
- 0:00Start
- 5:06TESTING PRIVATE METHODS - THE PROBLEM
- 5:52TESTING PRIVATE METHODS - ALTERNATIVES
- 6:28TESTING PRIVATE METHODS - EXTRACT SIMPLE CLASS
- 7:12TESTING PRIVATE METHODS - DEFER THE DECISION
- 7:55DUPLICATE TESTS - THE PROBLEM
- 9:21DUPLICATE TESTS - THE SHARED EXAMPLE GROUP SMELL
- 10:26DUPLICATE TESTS - THE DIRECT MODULE TEST SMELL
- 10:49DUPLICATE TESTS - THE EXTRACT CLASS FIX
- 11:08DUPLICATE TESTS - THE KEY IDEA
- 11:45INVENTING THE UNIVERSE - THE PROBLEM
- 12:06INVENTING THE UNIVERSE - THE PREMATURE FIX SMELL
- 14:08INVENTING THE UNIVERSE - SHARED CONTEXT SMELL
- 16:24INVENTING THE UNIVERSE - FACTORY_GIRL SMELL
- 20:36A MAGIC TRICK
