> No, not when I run the example out of the box - I had to move the
> PerlPassEnv directives to extra.conf.in and rebuild (this makes sense,
> though, as extra.conf is processed before modperl_extra.pl, while
> extra.last.conf is processed after - perhaps you fixed your local copy and
> haven't up
>> Have you had D::C collect coverage stats for tests in the t/apache,
>> t/response/TestApache format?
>
> yes. when I run the skeleton I pointed you toward last time I get this
>
> Filestmt bran condsub time total
> - -- --
Hilary Holz wrote:
Okay - here's what I've figured out - D::C is not recording any coverage
info when I run a test in t/apache. D::C is recording coverage for all the
tests that are in the t/ directory - and the reports are in the realm of the
reasonable.
Have you had D::C collect coverage sta
Okay - here's what I've figured out - D::C is not recording any coverage
info when I run a test in t/apache. D::C is recording coverage for all the
tests that are in the t/ directory - and the reports are in the realm of the
reasonable.
Have you had D::C collect coverage stats for tests in the t/a
> [snip - ah, helpful, now I understand how to use the testcover target]
:)
> Devel::Cover is reporting
> 100% statement coverage for a number of modules for which there are no tests
> as of yet (legacy modules I have yet to revisit)
I don't think that's unusual - D::C will aggregate all the r
> I've noticed that Devel::Cover reports wildly different results
> depending on the contents of @INC within the test files. Do you set
> search paths within the files?
>
Apache::Test sets the path (use lib '/yada/blib/lib') in modperl_inc.pl,
generated as part of the testing configuration. So t
On Fri, 2005-09-16 at 14:45 -0700, Hilary Holz wrote:
> Well, I've learned something, but I still have the same problem. Sigh.
>
> I'm running under Module::Build, using the testcover target. Devel::Cover is
> collecting coverage statistics on the modules, it's just collecting
> reporting wildly
Hi Geoff (& Paul),
On 09/16/2005 08:54 AM, "Geoffrey Young" <[EMAIL PROTECTED]> wrote:
> Apache-Test-based distribution. the first is the addition of
> t/conf/modperl_extra.pl which (for anyone searching the archives) contains:
>
> if ($ENV{HARNESS_PERL_SWITCHES}) {
>
[snip - ah, helpful, now
On Fri, Sep 16, 2005 at 11:54:00AM -0400, Geoffrey Young wrote:
>
> > I'd really love to use Devel::Cover - I love the effect mastering the
> > request/response Apache::Test framework has had on my code, and I really
> > want to start using code coverage as part of my toolkit.
>
> yah, this is a
> I'd really love to use Devel::Cover - I love the effect mastering the
> request/response Apache::Test framework has had on my code, and I really
> want to start using code coverage as part of my toolkit.
yah, this is a bit more complex than it probably ought to be, but I guess
that's by design.
I'm trying to figure out why the coverage reports I'm getting from
Devel::Cover (well, cover...) aren't recognizing the effects of most of my
testing. A simple example is one module for which Devel::Cover doesn't
record any subroutine coverage, yet I have tests for each of the subroutines
that run
11 matches
Mail list logo
