Academic TDD links

I have been reading through some of the academic literature on TDD and figured it might be useful to put up a quick little bibliography of what I am reading through.


White paper on Unit Testing R.Venkat Rajendran

Realizing quality improvement through test driven development

Actually quite a few here

Efficiency and Effectiveness Measures To Help Guide the Business of Software Testing

Effective Unit Test Minimization

On the Effectiveness of the Test-First Approach to Programming

Test-Driven Development- Concepts, Taxonomy, and Future Direction

A structured experiment of test-driven development

Idea Paper v.02 – An Analysis of Test-Driven Development

Quite a few here



Have some more important things to read through put them up!

This entry was posted in Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.

6 Responses to Academic TDD links

  1. In addition, see “TDD – The Art of Fearless Programming” article that summarizes several empirical studies (( and the entire IEEE Software issue dedicated to TDD (

  2. Philippe Hertzog says:

    The link concerning “On the Effectiveness of the Test-First Approach to Programming” doesn’t work for me. Unable to find the document you mention.

  3. Steve says:

    Thanks for the response, although I did notice that pretty much all those papers also cover TDD. Getting my department head to agree to Unit Tests is one thing, getting them to agree to TDD is another. :)

    My belief is that TAD is better than no testing at all, so I’ll take what I can get.

    To be honest, the best link could have been the Idea Paper, but it appears that the controlled test never happened. That would be have been perfect for what I was looking for. In the mean time 15%-30% cost up front to reduce bugs by 40%-90% will have to be good enough. I guess I’ll see how the bean counters feel about it.

    Thanks again for the links, they’ve been very helpful.

  4. Greg says:

    Steve, there are numbers in a few of those papers in particular “On the effectiveness ” … the quantify subjectively a 15-35% initial cost over no tests but show a direct correlation between number of tests and number of defects.

  5. Steve says:

    The big problem I’ve found with Unit Testing is that it’s hard for to quantify it’s ROI. When asked if it’ll increase the coding time, the answer is most definitely yes (although I think the numbers thrown around like 50% increase are miles too high). Most managers don’t even hear the “but it’ll save us time down the road” since all they’re too focused on the first part.

    If anyone has any links out there re: the benefits of Unit Testing that has numbers it’d be much appreciated if you could post them.

    A few of these links do that, but I was hoping for more.

    Thanks in advance

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>