Turning yourself into an user is often the best test
I think that trying the program by yourself, pushing it to its ends, while pushing yourself to yours thinking of what happens and can happen, is sometimes the best way you can afford to know in a reasonably short time frame if a program is good or not.
Digging into the code, even if you are a trained developer, can tell you only if you have the time to do it with really the care and effort this always implies if you want to be effective. Plenty bugs that have annoyed developer teams and users for years have come from that: too fast and superficial inspecting of code (no matter with which tools, from visual fast reading, to automated test sets) - when it's not too fast tweaking of the code...
Paris, Mon 15 May 2006 16:39:45 +0200