Jeff Bisbee wrote:
My
guess is that you need to add -I to your prove command to use the newer
version from the tarball and not your installed version
prove -Ilib -v t/*
Absolutely correct. The installed version (detected using your 'pmpath'
script mentioned in another recent thread) was 1.07.
Also I was thinking it would be nice to be able to run prove and
Devel::Cover together by possibly adding a -M to prove
prove -MDevel::Cover -Ilib -v t/*
I don't recall this -M/-m suggestion, but I like it.
Can someone please submit it to the CPAN queue?
Thanks,
xoxo,
Andy
--
Andy Lester => [EM
Jeff,
On Nov 5, 2004, at 4:33 PM, Jeff Bisbee wrote:
I was just wondering if there was an easier way where make test whould
like in lib and not blib.
Well if you don't do the 'make test' step, you can just call the test
file individually and add 'lib/' to the @INC from the command line.
Like this
* Stevan Little ([EMAIL PROTECTED]) wrote:
> I tend to not re-make my modules before I test them (then again, they
> are always pure perl so I don't need to do it as much in a C based
> module). I have a small shell script (run_coverage.sh) which just
> removes the cover_db folder, then loops th
> prove -MDevel::Cover -Ilib -v t/*
>
> I remember mentioning something to Andy, but at the time he didn't like
> it.
On a related note, I think an -M option to prove might be a useful
feature.
With my own test suite, I want to load and run a perl module
(TestConfig.pm) before each test scri
Jeff,
On Nov 5, 2004, at 10:46 AM, Jeff Bisbee wrote:
I'm also curious how other folks run coverage, update modules
and rerun coverage.
I tend to not re-make my modules before I test them (then again, they
are always pure perl so I don't need to do it as much in a C based
module). I have a small
On 2004-11-05, Jeff Bisbee <[EMAIL PROTECTED]> wrote:
>
> I remember mentioning something to Andy, but at the time he didn't like
> it. I'm also curious how other folks run coverage, update modules
> and rerun coverage.
Using Module::Build, it's easy to run coverage:
./Build testcover [test opt
* Jim Keenan ([EMAIL PROTECTED]) wrote:
> This is a report on differences between the output of
> 'make test' and 'prove' which are, well, different
> from those reported by Stevan Little in a thread
> beginning on Sept 4.
Are you sure the tarball and the installed version are the same? My
guess
This is a report on differences between the output of
'make test' and 'prove' which are, well, different
from those reported by Stevan Little in a thread
beginning on Sept 4.
While teaching myself how to use 'prove' tonight, I
decided to try it out on a Perl core module which I
have also been usin
On Fri, Sep 03, 2004 at 04:02:39PM -0400, stevan little wrote:
> I seem to have fixed the issue, it had something to do with the scope
> of some of the DBD specific variables. Basically, I had repleaced
> several use vars (...) with our $variable not realizing the variables
> were then being
I seem to have fixed the issue, it had something to do with the scope
of some of the DBD specific variables. Basically, I had repleaced
several use vars (...) with our $variable not realizing the variables
were then being file scoped and not package scoped. Once I got the
variables into the
I am getting ready to release a new version of DBD::Mock and all seemed
fine until I tried running 'make test' and I got a bunch of warnings,
which when I ran it with 'prove -b t/*.t' I did not get.
I have tried to debug the issue based on the DBI line number. But (as
far as I can tell) what
12 matches
Mail list logo
