Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Cockburn on Testing: Real Programmers have GUTs

Cockburn on Testing: Real Programmers have GUTs

This item in japanese

In an interesting follow up on the video which InfoQ posted about debate between Bob Martin and Jim Coplien on 'TDD, CDD and professionalism', Alistair Cockburn blogged on how too many people say 'TDD' when they really want to say that they have good unit tests (GUTs).

Alistair penned the following observation about the debate:

Bob, you started by saying TDD is writing the test before the code, and that it is the hallmark of the professional. At the end, you said the hallmark of the professional is to have good unit tests, and TDD is one way of achieving that.

He suggests that there is a  shift in assertion by Bob on what makes a true professional. Though Bob starts with TDD, he seems to agree that to be a professional you need to have good unit tests.

Alistair believes that, till date, there has been no good term for "good unit tests," as there is for TDD. Had there been a term like 'GUTs' for good unit tests then people could brag about GUTs without implying whether they were written before or after the code. In the extreme programming digest he mentioned:

The punchline is: we need a term for "I have good unit tests", distinct from when they got written.

Right now people who write unit tests make a strong distinction between those who write them before the code and those who write them after the code. A term like "GUTs" would help these two groups to come and talk on the same platform. Further, he mentions that, if that were the case, then:

... Bob could assert that having GUTs is the mark of the modern professional programmer. ...

... Bob could separately assert separately that TDD is a better way of getting GUTs, and ...

... Cope could counter that even mountains of GUTs don't cover the state space as well as CDD, ...

... etc ...

Alistair seems to agree that there is no discounting the fact that unit tests are important. Development teams might want to practice TDD or write test cases after the code, as per their comfort. What really matters is that they should have GUTs.

Editor's note: Like Archimedes, Alistair Cockburn had this Eureka! moment in the bathtub. He was reading our interview transcript at the time, proving that at least one Naked Agilist reads InfoQ. (Hint: follow the links, it will wipe that strange image from your mind :-)

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • GUTs at last

    by Antek Baranski,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I found this to be a refreshing look at Unit Testing as it’s something that I have been struggling with at my current work place where unit testing is note done, and talking about TDD is considered heresy.

    I still personally believe that TDD is the 'better' way of developing software, but the term GUTs may come very handy and act as a stepping stone for an organization that is used to shoot from the hip software development.

  • waiting for GT's

    by deepak shetty,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Ah well , maybe someday Alistair Cockburn will change his philosophy to say "I have Good Tests" and stop quibbling about whether a test is a unit, integration or a functional test , but atleast some progress has been made.

  • Re: waiting for GT's

    by Jonathan Allen,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I would be happy if people shut up about how important tests are and start talking about how to write good tests (of all varieties).

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p