Paul Johnson wrote:
> This is something that I too have asked for in the past. I've even
> hacked up my own stuff to do it, though obviously not as elegantly as
> you or Geoff. Here's my use case.
>
> I have a bunch of tests that generally pass. I hack something
> fundamental and run my tests. Loads of them fail. Diagnostics spew
> over my screen. "Urgh", I say. Now I could scroll back through them.
When faced with a tough problem it's often useful to go back check that it's
actually the problem and not a solution posing as a problem.
"Make Test::Builder die on failure" is a solution, and it's not a particularly
good one. It's hard to implement in Test::Builder and there's all the loss of
information issues I've been yelping bout.
The problem I'm hearing over and over again is "Test::Builder is spewing crap
all over my screen and obscuring the first, real failure". So now that the
problem is clearly stated, how do we solve it without making all that spew
(which can be useful) totally unavailable?
--
39. Not allowed to ask for the day off due to religious purposes, on the
basis that the world is going to end, more than once.
-- The 213 Things Skippy Is No Longer Allowed To Do In The U.S. Army
http://skippyslist.com/?page_id=3
