On Fri, Jun 25, 2004 at 01:07:36PM -0400, Andrew Pimlott wrote:
> You are also circumventing the isolation part of the xUnit model,
> because you don't get setup/teardown for each test data. Possibly you
> don't care about that in this case, but if you did, you wouldn't be able
> to do the above,
On Fri, Jun 25, 2004 at 10:13:52PM +0100, Adrian Howard wrote:
> On 25 Jun 2004, at 16:51, Fergal Daly wrote:
> [snip]
> >NB: I haven't used xUnit style testing so I could be completely off
> >the mark
> >but some (not all) of these benefits seem to be available in T::M land.
>
> Just so I'm clea
On Fri, Jun 25, 2004 at 02:18:49PM -0500, Andy Lester wrote:
> On Fri, Jun 25, 2004 at 04:51:29PM +0100, Fergal Daly ([EMAIL PROTECTED]) wrote:
> > > * I never have to type repetitive tests like
> > >
> > > isa_ok Foo->new(), 'Foo'
> > >
> > > again because it's handled by a base class that all
On Thu, Jun 24, 2004 at 12:45:26PM -0400, Vsevolod (Simon) Ilyushchenko wrote:
> Hi,
Hello,
> I've run into "Can't call method "add_statement" on an undefined value"
> running Devel::Cover. Apologies if this was reported before, but the
> list archive is not searchable. I am using perl 5.8.4 a
On Fri, Jun 25, 2004 at 11:07:06AM -0400, Geoffrey Young wrote:
> hi paul :)
>
> I recently discovered an issue with nested subroutines while using
> Devel::Cover with Parse::Yapp. the basic issue is that some subroutines are
> not discovered by Devel::Cover and thus no metrics are generated.
>
Absolutely correct. I was able to reduce the code to:
require B::Deparse;
B::Deparse->new->coderef2text(sub {})
The problem occurs because Devel::Cover overrides some of B::Deparse's
subs, but when you go calling them in a program it gets upset. The
solution is to only override the subs f
