Unselfish Testing

on YouTube ↗43m

" summary

Claim: many unit tests are unmaintainable and slow; concrete fixes and patterns improve signal and speed. Replace a loop over four customers with four tests so one failing assertion becomes three distinct failures, saving minutes (transcript example: ~3m45s to locate the value). Use one assertion per test, inline simple object creation instead of hidden setup, apply builders at suite level, and mock external resources (no filesystem/network/db). Add isolated “solitary” unit tests plus a few integration “sociable” tests; it works and keeps suites fast and debuggable.

AI-written summary · about

" chapters (8)

1. 0:00Start
2. 12:25Suite / Fixture / Test
3. 15:18one: replace loop with individual tests
4. 16:37two: expect literals
5. 20:12Motivators
6. 20:51code coverage
7. 21:27document the system
8. 22:28tdd break up a problem improved design

" related talks

• 40mUnselfish TestingJay Fields · GOTO Chicago 2015
• 44mTesting the untestable - patterns and use cases analysisPiotr Stawirej · JDD 2023
• 56mIf You Won't Test Your Code, Who Will?Scott Davis · Great Indian Developer Summit 2015
• 48mTesting Should Be FunNoel Rappin · RubyConf 2012
• 25mWriting Testable CodeBob Fornal · Commit Your Code 2025
• 01h 07mProperties of Unit TestsArne Mertz · NDC TechTown 2022
• 01h 05mMicrotestingMatt Davies, Rob Moore · NDC Sydney 2016
• 26mTesting the Tricky StuffSamuel Goodwin · Mobilization 8