I hate writing documentation. It contains the wrong information, not enough information, or too much information. It's in the wrong place at the wrong time and it confuses me. I'd much rather write code even though I know that documentation can be important too. But wait!

Tests are code. Tests can contain just about everything needed for code documentation. A runnable, up-to-date, continuously cared-for-documentation. So what do we need to think about in order to replace documentation with tests?

Recorded 12 March 2014 at the Booster conference in Bergen, Norway.
boosterconf.no

Loading more stuff…

Hmm…it looks like things are taking a while to load. Try again?

Loading videos…