SKIP blocks and the debugger

Does anyone else find that SKIP: { } blocks bugger up the debugger? I'll be happily bouncing on the n key to get to round about the vicinity of the failing test, and then blam, it sees a skipped test and just fast-forwards to the end. K. -- Kirrily Robert [EMAIL PROTECTED]

Re: SKIP blocks and the debugger

On Mon, Jan 09, 2006 at 07:06:08PM +1100, Kirrily Robert wrote: Does anyone else find that SKIP: { } blocks bugger up the debugger? I'll be happily bouncing on the n key to get to round about the vicinity of the failing test, and then blam, it sees a skipped test and just fast-forwards

Re: Set binmode on T::B's File Handles?

On 9 Jan 2006, at 05:03, David Wheeler wrote: [snip] Is there any way to get Test::Builder to set an I/O layer on its file handles? [snip] Y'want Test::Builder's failure_output(), e.g.: use Test::More tests = 1; binmode Test::More-builder-failure_output, ':utf8'; diag \x{201c}; ok 1;

Re: What about Test::Unit?

Thanks for the responses. I have indeed started to look at Test::Class. A major point raised here about Test::Unit is that it doesn't integrate with Test::Builder, which I hadn't considered. Another issue is that because TU so closely matches jUnit it is less Perlish, and I think that is