Conversely, you're not going to have a problem until you run the code. If it NEVER runs you will never have the problem.
I should think that testing attempts to run every piece of code.

Anyway, I do agree that design time or even compile time would be best, but I still think that this is better than nothing.


>You won't know until you run this part of code. So this makes it much harder to check that every variables are declared (if it's a programming standard).
>
>>Well I don't know about that... Sure, design time would be best, but it is upon running that people encounter the bad behaviour, and this can, at least, save lots of hair-pulling for hard-to-find typos as were described earlier in this thread.