As Test-Driven Development has gained in momentum and popularity, it has also been called into question as a viable development strategy past the first 3-4 iterations in Agile projects. Many report that the test suite generated by the process can become a maintenance problem in and of itself, eventually collapsing under its own weight. Is this an inherent problem with TDD, or simply a result of a misunderstanding of how TDD works, and what needs to be emphasized in order to keep it sustainable? We will examine this question in some detail, and offer some insights on overcoming this limitation.
Net Objectives' Scott Bain is a 30+-year veteran in computer technology, with a background in development, engineering, and design. He has also designed, delivered, and managed training programs for certification and end-user skills, both in traditional classrooms and via distance learning. Scott teaches courses and consults on Agile Analysis and Design Patterns, Advanced Software Design, and Sustainable Test-Driven Development. Scott is a frequent speaker at developer conferences such as JavaOne and SDWest. He is the author of "Emergent Design: The Evolutionary Nature of Professional Software Development" now available from Addison Wesley/Pearson Education
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?