Hi,

Comments are great, but they can become incorrect when not updated with 
code changes.

Tests always describe functionality by using and demonstrating it;
they can not lie.

So it could be a great opportunity for a documenting tool
like RDoc to browse tests and feature their information
as documentation near the documented methods.

The while thing could be optional, like -usetests testfile.

For example

assert_equal( (input/2), input.half)

says
"The method named half returns the result of receiver divided by 2."

This sentence could be included in the RDoc documentation for
this method.

For more complex tests, the relevant code fragments
could be included instead.

This is a very young idea; it might have potential,
but probably has complexities.

Tobi

-- 
http://www.pinkjuice.com/