Hacker News Reader

Comment by grammr | Hacker News Reader

Write code with testing it in mind. Testing is often introduced far too late in the programming learning process, if at all.

View on HN

Schools that have switched to the How to Design Programs (http://www.htdp.org/) curriculum for their intro classes would beg to differ! Of course, whether that specification+testing approach to development is carried through to the rest of the curriculum is another story :-)

Every book I read by a real-world programmer - never does this. They always put testing in a separate chapter or never address it at all, example: programatic programmers.

Even any tutorials online or in a user group - it's never done. It's always talked about. I come from a engineering background so I really wanted to programming the "right" way. But here is so little code that includes testing that I can use to "tutor" myself. Even opensource.

I find this very odd.

Have you looked at this Rails tutorial? http://railstutorial.org/chapters/

Source code control, deployment and testing are all baked into the tutorial from the very first section where coding is started. It's also available in print form.

Thanks, I will when I get back into rails. I have given up on it as of right now. It nice to know there are more resources that include testing than there were 2 years ago for rails.

I've always gotten the impression that TDD is one of those things that many people think they should do, but have a hard time making a habit (so it's not surprising it gets more talk than action).

Speaking of books, Real World Haskell covers testing pretty early on; granted, being Haskell, whether or not it qualifies as "Real World" is still a little subjective at this point.

If you're looking for resources to tutor yourself, there are some TDD katas out there (I admittedly haven't tried it myself, though) - http://www.osherove.com/tdd-kata-1/

Reply on news.ycombinator.com