Does your organization actively practice test-driven development (TDD)? Chances are, the answer is no- at least based on the results of a survey distributed at Stelligent’s TDD roundtable, which found that the majority (84%) of the survey respondents aren’t practicing TDD, and 79% said they do not measure code coverage for development projects.

Interested in gaining insight on the findings, Colleen Frye of SearchSoftwareQuality.com wrote a great article, “Barriers remain for test-driven development” asking several of the roundtable attendees why TDD wasn’t being practiced and what it would take to get organizations to do it.

When asked to elaborate on why the adoption is still slow going, Bobby Pantall, Lead Technology Consultant at CC Pace Systems Inc., remarked:

Organizations haven’t been sufficiently informed of the business benefits of TDD. In our experience, there is a popular misconception that it’s wasteful to spend so much time writing tests instead of pure functionality.

Luke Majewski, Director of Application Architecture at Intalgent, added:

The common thread when we have this discussion with other developers is their companies don’t do it because it doesn’t make sense financially. It isn’t until you complete a project fully, with good test coverage, that you really appreciate what it does.

What are your thoughts? Is your organization practicing TDD? If not, why?