Aristotle Pagaltzis wrote: > * Michael G Schwern <[EMAIL PROTECTED]> [2008-01-12 12:00]: >> Ovid wrote: >>> I'll go fix that diagnostic thing now. Unfortunately, I >>> think I'll have to violate encapsulation :( >> If you know how to fix it let me know, because other than >> enumerating each testing module you might use and lex-wrapping >> all the functions they export, I'm not sure how to do it. > > Set a flag that T::B should quit when the next test result is > about to be recorded?
I guess it works, but it leaves you dead halfway through another test function which is weird. >> One possibility involves taking advantage of $Level, so at >> least Test::Builder knows which is the test function the user >> called, and then, somehow, inserting the code necessary to >> cause failure when that function exits. I don't know how you >> insert code to run when a function that's already being >> executed exits. > > Load the debugger and set a breakpoint? Oh, good one. If the debugger wasn't so damned full of bugs that might just work as a general solution. -- Robrt: People can't win Schwern: No, but they can riot after the game.
