Why Going Agile Excludes TDD in Most Cases (Revised)

TestFortExpert by TestFortExpert on 05/28/2014

Why Going Agile Excludes TDD in Most Cases (Revised)

This the revised variant of the formerly written post about my thoughts on inconsistency of test-driven development applied to agile processes, modified according to our LinkedIn readers’ opinion.

The agile practice called test-driven development (TDD) suggests writing tests before actual program code. It can technically increase the agility of the developer or product project levels. Among other significant benefits, existing empirical literature about TDD has also demonstrated more robust code and increased productivity. However, results show that sometimes TDD adoption is difficult and its potential agility benefits are not readily available.

Let’s list the main points where agile excludes TDD:

Thus, the resistance to use TDD at first is due to inexperience and growth in the amount of work.
When no support for TDD is available, inexperienced developers slip back to no unit testing development, that’s why support is needed at least at the early stages.

Check out our related articles:

7 Virtues of Agile Testers That Drive Success and Innovation

7 Main Practices of Test Automation in the Agile World

Why Agile Development Fails Sometimes?

Who Said Agile Means Victory?

5 tips for agile test automation

We use cookies to ensure your best experience. By continuing to browse this site, you accept the use of cookies and "third-party" cookies. For more information or to refuse consent to some cookies, please see our Privacy Policy and Cookie Policy