Re: TDD: Test-Driven Design or Test-Driven Development?

From: Ron Jeffries (ronjeffries_at_REMOVEacm.org)
Date: 01/09/04 

Date: Fri, 09 Jan 2004 14:31:18 -0500

On Fri, 09 Jan 2004 10:40:48 -0800, Costin Cozianu <c_cozianu@hotmail.com>
wrote:

>How can you claim that, Don't you realize that XP has 0 defects by
>definition ?

Sarcasm may not be the best possible tool for professional discourse.

There really are XP teams running at zero known defects, and others running with
a bug list of one or two bugs. This from teams that used to have hundreds.

Something interesting is happening, and it might be wise to look into it.
>
>All the tests have to succeed, and then that's what the customer signs
>off on. If the tests run and are successful, then by their definition
>the software is perfect, there's nothing more that developer should work on.

There are features to work on, I would suppose.

What technique do you recommend for knowing when the software is done, if not
testing?
>
>Voila, the simplest way to create perfect software, or at least to let
>the developer off the hook :)

Unless there are zero bugs in your team's code, which would surprise me, the
result of following the rule of fixing all known defects actually puts
developers /more/ on the hook, not less.

Regards, 

-- 
Ronald E Jeffries
http://www.XProgramming.com
http://www.objectmentor.com
I'm giving the best advice I have. You get to decide whether it's true for you.

Relevant Pages

  • Re: TDD: Test-Driven Design or Test-Driven Development?
    ... > There really are XP teams running at zero known defects, ... If you test with intention to get things working you'll get it working ... (zero defects) ...
    (comp.object)
  • Re: quality control
    ... Almost always, zero. ... How did you go from 100 samplings of size 100 to the number 1400? ... that there are *no* defects, than what you get with this strong ... Phyperis a cumulative probability rather than a single table ...
    (sci.stat.math)