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? In this presentation we will introduce the basics of automated test-driven development, and then briefly examine the specific factors that make it a sustainable process. This requires more than simply knowing how to write unit tests, but implies a style of test design that does not become un-maintainable as the test quite matures and grows in size.
