One point I think people have overlooked is that you don't need to understand a bug before writing a test for it. All you need to know is how to reproduce it. A unit test is simply a way of automatically running some subset of the program (which could even be the whole thing) with canned data and checking to see if the bug is still there.
Debugger or no, you can't properly fix a bug until you can reproduce it, and a unit test is the best way to document how to reproduce it.
Flat View: This topic has 90 replies
on 7 pages