This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Sharon Ross: Vincent, With your background, does your book take the point of view of an agile developer? Or can it be applied to a more "traditional" development environment? Thanks, Sharon
Hi Sharon, I've tried to make it agnostic in term of development methodology. However, you'll still find that there are quite a few references/demonstrations on how to perform continuous integration or rather how to automate testing and how it fits in the overall development process.
-Vincent<br /><a href="http://www.manning.com/massol" target="_blank" rel="nofollow">JUnit in Action</a> author
I was under the impression that Unit testing in an agile development was the same as for a traditional one - although you will do it more often.
Different processes state the need and method for writing unit tests a bit differently. XP, for example, encourages test-driven development in which you write the unit tests before the corresponding production code. Another process could encourage writing unit tests after writing the code. Most process instances in use probably don't say explicitly when the unit tests should be written (or how often). Besides, a process can be agile even without unit testing.