From: "Hal E. Fulton" <hal9000@...>
Date: 2002-09-18T12:12:51+09:00
Subject: Code coverage in Ruby?

Has anybody worked on a method for determining
code coverage in a Ruby program?

This is where defadvice might really come in
handy, I think.

Even if it was only at the method level, it
would be better than nothing. I'd prefer the
statement level.

I frequently find that a program "seems" to be
running fine, then I suddenly hit a runtime
error. 

On a side note: My most common one is that a 
method is not implemented for nil. This, I guess, 
is the equivalent of the most common runtime 
error in the "pointerless" Java language, which
is a null pointer exception.

My second most common runtime error is that a 
constant or variable is not defined.

Of course, XP fans might say that if my tests
were adequate, I wouldn't be worrying about it.

I'm not much of an XP person yet, though. I've 
never grasped how to write unit tests for GUI 
apps, for instance.

Hal