Test-Driven Heresy – lapses from the TDD are more forgivable the closer you are to the beginning of a project – Tim Bray
Sin and Penitence · People introducing TDD do this thing where they start from scratch saying “We’re going to write a class to do X and it’ll need a method to do Y, so let’s write a test for Y”. The problem is, when I’m getting started, I never know what X and Y are. I always end up sketching in a few classes and then tearing them up and re-sketching, and after a few iterations I’m starting to have a feeling for X and Y. ¶
And maybe the sketch-and-tear process would be better and more productive if I had the patience to write the tests for each successive hypothesis about X and Y, but I don’t think I ever will. This is partly because the first few tests for the kind of classes I write tend to be expensive; where you have to face the dependency-injection and big-fat-mock problems. I lack the patience to make that investment if I’m unsure the class is basically pointing in the right direction.
(Link: Test-Driven Heresy – lapses from the TDD are more forgivable the closer you are to the beginning of a project – Tim Bray)
Related posts:
- Infinitest – a continuous test runner for JUnit tests Welcome to the home of Infinitest, a continuous test...
- ongoing by Tim Bray · HTML5 and the Web Let’s Do Scenarios · What’s the best thing that...
- Mastering Grails: Mock testing with Grails In this article, you’ll learn how the mocking capabilities...
Uncategorized
