TDD has long been recommended by agile practitioners, but the community still argues about how to go about it. Insideout or outsidein? Mockist or classical? Through a component’s public API or for every class?
And then there’s Kent Beck’s famous quote “get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence.” This introduces a further level of subjectivity especially since developers are frequently overconfident. In Douglas Adams’ Hitchhiker’s Guide To The Galaxy the dolphins leave planet earth before it gets destroyed, with their last enigmatic message “So long, and thanks for all the fish” being misinterpreted. Is our software giving us the same message? After all, the software would still perform the same function without the tests, wouldn’t it?
In this session we’ll explore the choices that agile teams need to make when considering which development practices to adopt. We’ll look again at some of the arguments for the different approaches and I’ll urge teams to practice, practice, practice until you’re happy with the way you code.