Slashdot Mirror
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?
Like this goatse.cx links.
well..
Your use of language is clunky and stunted, which makes it hard to read. This has the hallmarks of a good troll though, so keep it up. Try posting it earlier in the thread next time though!
Deferred!!!!!!!
Another slashdot stories which says
"Jeez, maybe I should have trained in the stuff before trying to do it as a job"