Michael G Schwern wrote: > 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?
This is one of the reasons I wrote Test::Depends - it means that for instance if you have a module load failure, the later tests all fail with a smaller message. I personally have very little sympathy for people who can't write "or die" at the end of their assertions (or, better, "or skip ..."). ESPECIALLY if a side effect of catering for them impacts on the way harness works. Sam.
