
I tried, actually, but couldn't figure out how to separate running the
test from printing its output. All the attempted patches turned into
huge refactoring marathons.
When given the choice between sending a huge "replace all your code
with my code" patch, and just releasing a separate package, I prefer
to do the second. There's usually a reason a library behaves as it
does, and this way both behaviors are available to users (even if I
find one frustrating).
On Wed, Aug 10, 2011 at 23:51, Max Bolingbroke
On 11 August 2011 05:17, John Millikin
wrote: This is just a quick package I whipped up out of frustration with test-framework scrolling an error message out of sight, for the millionth time.
Patches to make test-framework less noisy (either by default or with a flag) will be gratefully accepted, if anyone wants to give it a go :-)
Max