There Are No Tests
summary
Claim: four out of five apps have zero or ineffective tests. Concrete fixes include adding unit tests for validations, relationships, and helpers; running metric_fu/flog/flay to spot a 36‑complexity hotspot; making deployment one‑command and running metrics on CI; treating bug reports as cucumberable integration tests and using screencast reports. Expect short‑term development to slow (~30% construction) but maintenance to speed (Microsoft: ~15% slower dev, ~60% faster maintenance). Start by writing one test, add pending specs, and measure coverage, velocity, faults, response time, and business value.
AI-written summary · about
chapters (4)
related talks
01h 05mMicrotesting
41mHigh Cost Tests and High Value Tests
33mDevs should love your tests
45mTesting the web without testers — success or failure
42mUse testing to Develop Better Software Faster
39mWeb Apps don't need no manual testing
33mThinking of your tests as a software product
10mBeyond “try harder”: Effective strategies to tackle bugs