Meh. Among the other reasons for testing the author didn't touch on: * It's not always about the tests. I TDD code (functional as well as OO - hell procedural

Meh. Among the other reasons for testing the author didn't touch on: * It's not always about the tests. I TDD code (functional as well as OO - hell procedural come to that) as a design tool - not a testing tool. I write acceptance tests as tools to help us understand when we reach "done" and as ways to track progress. * It's about stopping regressions. Test suites get in the way of accidental behaviour changes. * There a way to scale team communication of how the code should behave. I love FP dearly, but if it replaced testing why do I see so much FP code with test suites ;-)