in reply to Solving problems and fixing bugs

Building a testcase can sometimes be way too difficult to begin with (go test a gtk+ app or something even more scary). Step 7 seems most important anyway.

Replies are listed 'Best First'.
Re^2: Solving problems and fixing bugs
by dragonchild (Archbishop) on Mar 24, 2008 at 17:42 UTC
    If you can't see your way to building a testcase, then your code was built wrong. GTK+ apps, to use your example, are testable using any number of scriptable GUI testers (such as Rational Rose or, on OSX, Automator). Webapps are similar testable using Selenium. Come back when your problem deals with threads and random data.

    My criteria for good software:
    1. Does it work?
    2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?