Test-driven development is generally regarded as a good move: it should result in simple decoupled design, your tests tend to cover behaviour not methods, and far fewer bugs. However, just getting unit tests in on a real, commercial project is hard - switching to TDD is even harder. We'll examine how we can make small but permanent steps towards full TDD, without losing that progress when deadlines hit. We'll also cover a few methods for learning on your own time and how the whole process can actually be made quite enjoyable.

Comments

Comments are closed.

Rated 4

Anonymous at 14:09 on 29 Feb 2012

Rated 4

Anonymous at 14:10 on 29 Feb 2012

very good rhythm, and good points raised (the human factor of introducing tdd to your team, how to sell the tests to the client, etc...)
thanks !

Nice presentation, might have been a bit better with more business oriented content than on actual TDD

Nice pres. Now I have the tools to go back to my team and implement TDD.

Rated 5

Anonymous at 14:55 on 29 Feb 2012

Great talk.

Only caught the tail-end of the talk, but I especially liked the "Be prepared to fail" aspect, and giving points on how to cut your losses when things do go wrong. You're right to turn people to the Ruby community for how to grow software with TDD.