Re: Clover plugin glitches

[Ben Walding]

Although not terribly useful, occasionally looking to see how many of 
your tests are running can be elucidating.  If the tests aren't running 
/ logic in them isn't running, why is it there?  Are you not testing 
logic paths that you thought you were testing? (i.e. test code isn't 
running, hence the actual code that those tests run possibly isn't 
running through all the variations that you want it to run).

I'd definitely have it off by default though.

Caveat: I've never used Jester...

Jason van Zyl wrote:

On Wed, 2003-12-03 at 19:58, Ben Walding wrote:
 

This can be useful behaviour. It should be optional though.
   

How so? Just never thought about it myself really. But it should be off
by default. If you want to check the integrity of your tests we could
use something like jester.
 

Jason van Zyl wrote:

   

Vincent,

It looks like you were the last to modify the clover plugin and it seems
to be instrumenting and reporting on test cases as well. Is this
intentional?


     



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]