From: Ryan Davis <ryand-ruby@...>
Date: 2009-12-31T14:33:02+09:00
Subject: Re: Test::unit assertion pass scenario


On Dec 30, 2009, at 20:05 , John Smith wrote:

> Why is a good question. First, the extra info is not for myself, nor 
> would it be for any of the devs who may run it. The theory is that 
> anyone who writes the test or uses them regularly should be familiar 
> with what is being tested anyway, and hence, only the failures really 
> need further investigation.
> 
> It's more of a CYA item for those who are, shall we say, not in the 
> know.

Some sort of detailed report of exactly what assertions you're running isn't a very good CYA. You might be better off with:

+ # of tests
+ # of assertions (or better: assertions / test)
+ % of coverage (possibly add heckle #'s, but that's a serious PITA)
+ loc test / loc impl (but please for gods' sake refactor both sides)
+ test time

and then graph that over time.