Unselfish Testing

on YouTube ↗40m

" summary

Tests that are hard to read come from over‑DRYing: loops, setup fixtures and object‑mothers hide failures and force navigation. Recommendation is concrete: replace looped assertions with separate tests, inline expected string literals, use solitary unit tests (mock dependencies with Mockito or simple stubs) for speed and isolation, keep a few sociable integration tests for coverage, and prefer one assertion per test. Aim for suite runs under a few seconds, move shared builders to suite level, and delete flaky low‑ROI tests.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 0:36When Do We Run Our Tests
3. 12:49Applying Dry at the Suite Level
4. 16:15Expect Literals
5. 16:55Inline a Setup
6. 20:30Customer Acceptance
7. 24:47Solitary Unit Tests
8. 25:25Cascading Failures
9. 32:16How Else Can You Improve the Test Suite
10. 38:15Stop Thinking about Your Test from the Individual Point of View

" related talks

• 43mUnselfish TestingJay Fields · GOTO Copenhagen 2015
• 48mTesting Should Be FunNoel Rappin · RubyConf 2012
• 26mTesting the Tricky StuffSamuel Goodwin · Mobilization 8
• 44mTesting the untestable - patterns and use cases analysisPiotr Stawirej · JDD 2023
• 40mWrite awesome testsJeroen Mols · droidCon Berlin 2019
• 01h 07mProperties of Unit TestsArne Mertz · NDC TechTown 2022
• 01h 05mMicrotestingMatt Davies, Rob Moore · NDC Sydney 2016
• 26mKeeping Your Tests LeanMeaghan Lewis · SeleniumConf Berlin 2017