Slashdot Mirror

← Back to Stories (view on slashdot.org)

Properly Testing Your Code?

Posted by Cliff on from the hope-it-gets-a-passing-grade dept.

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?

9 of 470 comments (clear)

  1. The most effective way... by rattler14 · · Score: 3, Funny

    before each compile, one should make a small sacrifice to the debugging gods and ask them to forgive you for your syn(tax).

    --
    my last sig was too controversial... now, a new and improved useless sig!
  2. Just use the Microsoft way... by cliveholloway · · Score: 3, Funny
    They use Beta testers - the have the largest group of Beta testers out there - otherwise known as their customer base :)

    boom boom

    cLive ;-)

    --
    -- Trinity in high heels carrying a whip: The donimatrix - there is no spoonerism
  3. It's easy by cca93014 · · Score: 1, Funny

    If it compiles, its fine! VB's great isn't it?

    I never did learn what segmentation fault meant at college.

    --

    Invoicing, Time Tracking, Reporting

    1. Re:It's easy by Anonymous Coward · · Score: 1, Funny

      on error resume next

      What errors?

  4. 101 little bugs in the code by NeilArrow · · Score: 2, Funny

    Just to emphasise how good design is the key to avoiding most bugs, not testing - there's a song that often gets sung at my place of work...

    Hundred and one little bugs in the code
    Hundred and one little bugs in the code
    Fix the code, compile the code
    Hundred and two little bugs in the code

  5. Re:the best way to test code... by protonman · · Score: 3, Funny

    No that's gravity.

    --
    The man of knowledge must be able not only to love his enemies but also to hate his friends.
  6. Re:best way to test is to use automated testing by Flamesplash · · Score: 2, Funny

    Maybe when we have quantum computers we can test every single user scenario in parallel

    -flamesplash

    --
    "Not knowing when the dawn will come, I open every door." - Emily Dickinson
  7. Let the User's Do It by John+Hasler · · Score: 5, Funny

    "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"?

    --
    Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
  8. Correctness... by richieb · · Score: 3, Funny
    Building correct software from requirements is as easy as walking on water. As long as they are frozen. :-)

    --
    ...richie - It is a good day to code.