http://mattstine.com/2009/10/03/test-driven-development-worked-for-me/ Thoughts on Java, Groovy, Grails, Agile Development, etc. etc. etc. Tue, 17 May 2011 16:24:45 +0000 hourly 1 http://wordpress.com/ http://mattstine.com/2009/10/03/test-driven-development-worked-for-me/#comment-84 Thu, 08 Oct 2009 23:41:54 +0000 http://www.mattstine.com/?p=254#comment-84 Defect Driven Testing (DDT) is really a good place to start. To write test for a bug, DDT make you think the test code is really doing something useful and then you are willing to spend more time on it. We actually did that even though we didn’t know the term at the time. We were using EJB2 and you know to test EJB is not that easy. You need to really realize the important of testing to put those effort writing test code for EJB. We had pretty OK testing coverage for back-end APIs. TTD is even better, I believe Matt will lead our team to get there.

]]> http://mattstine.com/2009/10/03/test-driven-development-worked-for-me/#comment-83 Mon, 05 Oct 2009 14:42:30 +0000 http://www.mattstine.com/?p=254#comment-83 … according to Michael Feathers TDD was even reported to be successful at Microsoft, where they plan new products top-down to the class level. It’s still worthwhile to write the pre-specified component using TDD (if only to uncover contradictions in the specification)!

]]> http://mattstine.com/2009/10/03/test-driven-development-worked-for-me/#comment-82 Sun, 04 Oct 2009 12:12:08 +0000 http://www.mattstine.com/?p=254#comment-82 To get someone infected on any matter, just start doing it ourself and show what the benefit is in practice. I cannot imagine that someone could refuse to accept CI as its benefit is obvious.

]]>