Re: TODO test paradox: better TODO test management?

On Tuesday 31 January 2006 13:31, A. Pagaltzis wrote:

> Hmm. That’s a good point. Maybe the way to approach this would be
> to include a default harness for use by developer tools, which
> would include more chattiness about passing TODO tests.

My perfect developer tool would complain noisily about failing tests (and give 
all of the diagnostic information for me to debug them), highlight bonus 
tests (and give the diagnostic information for me to promote them), and 
summarize everything else.  If it passes, increment the counter but don't 
tell me.

How would that work for you?

-- c