Harry Baran from Thoughtworks posted a blog that I think is very much worth sharing. Harry outlines in his posting some of the difference between unit testing in Agile to the Traditional approach.
Unit testing in any process needs to be getting the attention it deserves, if done right it can be an early quality indicator for the solution under development. Test teams need to get involved in unit testing to some capacity no matter what process/methodology being followed. Pair up your developers and testers, offer training to your testers in unit testing and coding, hire testers with coding skills, let your testers see and understand what is being unit tested.
To quote Harry Baran: “Unit tests are foundations of an agile project. They enable fast feedback, continuous testing, continuous integration and refactoring.”
As children we were taught to share, for some reason one of the most important aspects of developing an application has not been shared. Time to change that, isn’t it?
Unit Testing: Agile vs. Traditional Approach
Great write up Hari, thanks,