Re: how many bugs do you find and correct during TDD?

From: AndyW (foo__at_bar_no_email.com)
Date: 01/01/05 

Date: Sat, 01 Jan 2005 12:56:07 +1200

On Fri, 31 Dec 2004 13:22:44 GMT, "Phlip" <phlip_cpp@yahoo.com> wrote:

>
>"AndyW" <foo_@bar_no_email.com> wrote in message
>news:nm7at0ddnue4uiserb31vr87nh93gft7rq@4ax.com...
>> On Thu, 30 Dec 2004 15:16:51 -0800, Tammy <qqq@ppppp.com> wrote:
>>
>> >
>> >
>> >AndyW wrote:
>> >> Last year I had 3 defects for the whole years worth of coding, before
>> >> that was an unusal year and I had 5 defects. I dont do TDD, I just
>> >> write code properly in the first place :)
>> >
>> >I don't mean how many bugs were seen by QA or customers, i mean
>> >how many bugs did you generate during the development process,
>> >regardless of who found them.
>>
>> Thats what I am talking about. I use metrics and other developer
>> techniques to identify defects before and during coding. Usually when
>> I submit code for the testers I can tell them what the probability is
>> that a defect will exist and where it will be (testers really hate it
>> - but you only have so much time as a developer and its not possible
>> to cover all the bases).
>>
>> Last year I submitted 8 defects that were over 80% probability and 3
>> eventuated (2 at the start of the year and I had a sulk going for 3
>> months).
>
>Props. However, code should be more than bug free.
>
>How easily could you...
>
> - not help someone else add a feature to your code?
>
> - interrupt a coding session to deliver a version to end users?
>
> - minimize the time between specifying a feature and delivering it?
>
> - make an unplanned change and re-verify everything?
>
All a doddle. Although the unplanned change is pretty hard to do
because in my book they are a very very rare event indeed.

Changes are pretty easy to forecast quite some time in advance if you
have the correct relationship with the right people and a good
business sense.

>Note I'm not saying doing those are all good things to do. But code ready to
>do them is usually extraordinarily bug-resistant.
>
>If your code indeed has those abilities, we'd love to hear how you do it.
>One more bullet point on the list is How easily can you teach others to
>replicate your process?

Its fairly easy and usually part of my job. Hardest part is teaching
people about metrics, second hardest part is teaching developers
business and project management skills so they understand the metrics.

Coding actually makes up between 20% - 40% of my time on average with
the the middle figure being the norm. If you are doing more than that
as a developer then your probably not doing the things you need to be.
>
>> Normally I'd go for 100% defect free but there is a time/effort trade
>> off where you just have to go for fit for purpose.
>
>In my experience, maintaining high scores for my checklist is also a good
>way to push up to that last 99.9%.

Relevant Pages

  • Re: how many bugs do you find and correct during TDD?
    ... >> that was an unusal year and I had 5 defects. ... I use metrics and other developer ... techniques to identify defects before and during coding. ... I submit code for the testers I can tell them what the probability is ...
    (comp.object)
  • Re: The Economics of Incompetence
    ... professionals are barely competent. ... billy junior didn't write an adequate unit test, ... are 20 new defects in the defect tracking system. ... the Lead Developer and start eating up his time. ...
    (microsoft.public.dotnet.general)
  • Re: identifying factors for tester evaluation
    ... Managers have plenty of other ways of evaluating their people and such individual metrics are easily abused. ... The fact that a particular developer had 0 defects where all the rest had 8-12 was a process issue, ... For major bugs give 3 numbers ... By the time the individual tester is implementing or running test cases the work has already been done. ...
    (comp.software.testing)
  • Re: The Economics of Incompetence
    ... billy junior didn't write an adequate unit test, ... are 20 new defects in the defect tracking system. ... Time to review the defects, ... the Lead Developer and start eating up his time. ...
    (microsoft.public.dotnet.general)
  • Re: Static vs. Dynamic typing (big advantage or not)---WAS: c.programming: OOP and memory management
    ... There is no question that static typing ... > The price of those benefits is that the developer has to sometimes "work ... > proportional to the number of defects detected. ... not enforce the type system and if the compiler does not depend on it ...
    (comp.object)