David Heinemeier Hansson

Practice religious test-first development for a month
Test-driven vs test-first 5 years ago

I’ve been a test-driven developer for quite a while, but I haven’t really gotten into the religious test-first branch yet. Usually, I’m too impatient. I have a good idea and want to execute on it right away. Then, when I see it in code, I’ll come back to do the tests.

I have done short spurts of test-first - some tasks just seem to invite it - but not as a regular approach over a longer and sustained period of time. I want to give that a try. For a month. Where I can’t write any code until I’ve seen a test fail.

Jan 03, 2005, 09:49AM PST


Comments:

Daniel Spils

Any luck yet?

I’ll be interested to see if the test-first religion can hold for a month. Give us an update when you’re 30 days into it …

Jan 21, 2005, 05:46PM PST | Respond to this

pate

How's it going?

Don’t wait until you’ve finished your 30 days. I’d like to know how your doing as you start coding test-first. What makes the transition harder or easier? Leave some guide posts.

Jan 28, 2005, 05:33PM PST | Respond to this

John-Mason Shackelford

Yes, it works great with Rails

I have been writing my Rails code test first for quite some time. One of the things I really like about rails is that even the functional tests can be written test first—whereas many functional test frameworks require that the app is working before the testing can be in place.

David, I mean no offense, but I am not sure I understand how code can be test driven without being test first. I don’t think Kent Beck would agree. I do agree that there is real benefit in having tests or ‘test while’ but unless you’ve written the test first, how can the test be driving?

Jan 13, 2006, 10:21AM PST | Respond to this 1 cheer


 

I want to:

The world wants to...

43 Things Login