Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Re: A danger of test driven development.

by pg (Canon)
on Oct 03, 2005 at 15:35 UTC ( [id://496966]=note: print w/replies, xml ) Need Help??


in reply to A danger of test driven development.

You are obviously doing the right thing, but need to employee a better plan.

I would guess that part of the problem is that you have enough test cases to cover the normal situations, but not enough to cover the exceptional situations.

  • Comment on Re: A danger of test driven development.

Replies are listed 'Best First'.
Re^2: A danger of test driven development.
by Your Mother (Archbishop) on Oct 03, 2005 at 17:05 UTC

    I agree w/ pg.

    The code came quickly back to me. Remember the hairy code I changed to pass the tests? Well, it was correct after all, and I broke it. The tests turned out to be wrong.

    It sounds like you had missing tests. If the field testers found a bug the code tweak introduced, there was a missing test case to match whatever it was they did to uncover it. For my own part, I have found meta-tests (like for the final object state or something; more like a user would see) to uncover bugs in my code better than micro-tests (checking return values from subs/methods; more like the hacker sees).

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://496966]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others examining the Monastery: (4)
As of 2024-04-23 22:25 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found