Properly Testing Your Code?

lowlytester asks: "I work for an organization that does testing at various stages from unit testing (not XP style) to various kinds of integration tests. With all this one would expect that defect in code would be close to zero. Yet the number of defects reported is so large that I wonder how much testing is too much? What is the best way to get the biggest bang for your testing buck?" Sometimes it's not the what, it's the how, and in situations like this, I wonder if the testing procedure itself may be part of the problem. When testing code, what procedures work best for you, and do you feel that excessive testing hurts the development process at all?

Comments

Let the User's Do It

[John Hasler]

"When testing code, what procedures work best for you,..."

Make sure it compiles and runs and then upload it to Debian/unstable.

(Yes, I'm joking).

"...and do you feel that excessive testing hurts the development process at all?"

If didn't hurt why would you label it "excessive"?