From: Phillip Gawlowski <pg@...>
Date: 2009-12-31T10:47:03+09:00
Subject: Re: Test::unit assertion pass scenario

On 31.12.2009 02:41, John Smith wrote:
> Yep, the example below is exactly the way I'm using it.
> However, as demonstrated in your example, the 259 assertions that were
> run (and passed) do not display any kind of passing checkpoint, the way
> it would have if any of those assertions failed.
>
> Basically, I am looking for a way to provide info just for both passed
> and failed assertions, similar to what is done when an assertion fails.

Why?

If an assertion passes everything is well (within the test parameters, 
anyway ;) ), and no action is required.

In fact, you'd drown out, since you degrade the signal/noise ratio, 
actual failures.

If you are looking for a way to see what code gets exercised (and if all 
code gets tested), RCov (used to be) a good solution (alas, it hasn't 
been updated since 2007) to test for code coverage, too.

--
Phillip Gawlowski