Re: testing module loading output and testing under the debugger

If you would like to use the standard debugger, you might find DB::typeahead useful for scripting purposes. There's also the recent perl5db.t to take a look at for an example of usage. Just a thought. > > > Not true. If you real perldebguts you'll see that the debugger can be > > scripted or y

Re: Uncoverable syntax (was Re: testing module loading output and testing under the debugger)

On Dec 20, 2006, at 11:06 AM, Michael G Schwern wrote: Well, maybe not exactly - I can probably make good arguments for inline annotation. Allow me. :) The current scheme won't track changes to the source file well. Using file + md5 rather than file + line helps some, but problems rema

Uncoverable syntax (was Re: testing module loading output and testing under the debugger)

Paul Johnson wrote: >>> 1. Find some nice way expressing what is uncoverable. For subroutines >>> this is easy. For statements it is not hard. For branches it is >>> tricky and for conditions I'm somewhat stumped. The current >>> method I use is based on implementation details.

Re: testing module loading output and testing under the debugger

On Wed, Dec 20, 2006 at 08:31:44AM -0500, Michael G Schwern wrote: > Paul Johnson wrote: > > That would be the "uncoverable" feature, which I haven't quite finished > > yet. It does just what is asked for, that is you can mark constructs as > > uncoverable which means that the sense of the error

Re: testing module loading output and testing under the debugger

Paul Johnson wrote: > That would be the "uncoverable" feature, which I haven't quite finished > yet. It does just what is asked for, that is you can mark constructs as > uncoverable which means that the sense of the error is reversed - the > construct will be in error iff it is executed. > > Ther

Re: testing module loading output and testing under the debugger

On Tue, Dec 19, 2006 at 04:17:07PM -0800, chromatic wrote: > On Tuesday 19 December 2006 16:04, Joshua ben Jore wrote: > > > It'd be nice if there were a pragma or function for use by > > Devel::Cover which said just that: cond ? ... : cond ? ... : cond ? ... : can't::happen; sub can't::ha

Re: testing module loading output and testing under the debugger

On Tuesday 19 December 2006 16:04, Joshua ben Jore wrote: > It'd be nice if there were a pragma or function for use by > Devel::Cover which said just that: Nicer yet would be if Devel::Cover (and I haven't tried in a few months; too busy with other things, so if there's a fix now, not only will

Re: testing module loading output and testing under the debugger

On 12/19/06, demerphq <[EMAIL PROTECTED]> wrote: On 12/19/06, Nadim Khemir <[EMAIL PROTECTED]> wrote: > >Personally I wouldn't get /too/ hung up about 100% test coverage - it > >can be taken too seriously. See Brian Marick's "How to Misuse Code > >Coverage"

Re: testing module loading output and testing under the debugger

On 12/19/06, Nadim Khemir <[EMAIL PROTECTED]> wrote: >Personally I wouldn't get /too/ hung up about 100% test coverage - it >can be taken too seriously. See Brian Marick's "How to Misuse Code >Coverage" for example. Thanks for the article link. I've

Re: testing module loading output and testing under the debugger

Hi Josh, > Not true. If you real perldebguts you'll see that the debugger can be > scripted or you could write your own debugger. right and right but Devel::Ebug is simply much cleaner and I'd rather not mock a debugger when I can use a real one. Hi Adrian, >> The first problem I have is captu

Re: testing module loading output and testing under the debugger

On 12/17/06, Nadim Khemir <[EMAIL PROTECTED]> wrote: I will also have a bunch of tests that need to be run under the debugger. I will use Devel::ebug as it is the only way to control the debugger. There are tests in the ebug distribution that I might be able to copy but I would also like to try t

Re: testing module loading output and testing under the debugger

On 17 Dec 2006, at 20:46, Nadim Khemir wrote: [snip] The first problem I have is capturing the module output when it is loaded. I tried: [snip] You might want to look at Test::Output for this. [snip] I will also have a bunch of tests that need to be run under the debugger. [snip] Why? (