David H. Adler wrote:
Mine is in
/usr/local/lib/perl5/site_perl/5.8.5/darwin-2level/Devel/Cover.pm
On OS X (and other systems, I'm sure) stuff sometimes gets installed
under architecture specific directories like that.
As mentioned elsehwere, perldoc -l is your friend.
dha
Yes, as I
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
[EMAIL PROTECTED] (Paul Johnson) wrote in message
news:[EMAIL PROTECTED]...
You can also try 0.50 at http://cpan.alternation.net/ppm/Devel-Cover.ppd
1. I couldn't figure out how to install that. The procedure I used,
per Crazy's instructions, to install 0.47
perl -MExtUtils::Install
Andy Lester wrote:
I have a modest proposal.
Stop calling the 2nd parm to ok() the name. It's really a comment.
I concur. I'm giving a talk next week which will in part be about
testing in Perl, and I will describe the second argument (actually, in
some Test::More functions, the *final*
Leif Eriksen wrote:
Hi,
I am doing some testing under Devel::Cover, and get some weird
results sometimes. What should I be looking at in my code or test cases
that is provoking this discrepancy?
Here's a link to the posting I did on Devel::Cover several months back
to which I referred a
Leif Eriksen wrote:
Hi,
I am doing some testing under Devel::Cover, and get some weird
results sometimes. What should I be looking at in my code or test cases
that is provoking this discrepancy?
Without D::C
++
[snip]
All tests successful.
Files=13,
Michael G Schwern wrote:
Anyhow, point is I know what the Phalanx project is but other authors might
not. It may be a good idea to send out a little note to authors who have
been Phalanxed explaining what the Phalanx project is all about and letting
them know they might see a sudden spike in test
David Cantrell wrote:
Jim Keenan wrote:
Using the standard Test::More framework, is it
possible to test whether what was printed to a
filehandle matches a predetermined string or list of
strings?
Would IO::Capture be of help here?
Looks promising. Hope to find time today to try it out and report
David Cantrell wrote:
Jim Keenan wrote:
Using the standard Test::More framework, is it
possible to test whether what was printed to a
filehandle matches a predetermined string or list of
strings?
Would IO::Capture be of help here?
And here are the fruits of my application of IO::Capture: a
David Golden wrote:
My $0.02:
Very nice integration of IO::Capture.
I think this is very promising, but all the start(), stop() calls seem
overly repetitive to me.
Agreed.
What about refactoring it into a set of test
functions that handle it for the user automatically? Just quickly off
the
Tels wrote:
On Friday 11 February 2005 21:08, David H. Adler wrote:
Just askin'. :-)
In similiar line of thought:
Why verify_number_lines instead of the (much shorter :) lines?
Speaking source code is something I like, but it shouldn't gabble on :)
Oh, and why TestAuxiliary and not
David H. Adler wrote:
A question: is there any reason that you made this an OO module but
still show calls to the methods as functions rather than methods on the
object?
An answer: It was a quick hack based on my first day's experience with
IO::Capture::Stdout. Its original rationale was
Fergal Daly wrote:
I was thinking of knocking together Test::AnnounceVersion.
use Test::AnnounceVersion qw(A::List Of::Modules);
which results in
# using version 1.5 of A::List
# using version 0.1 of Of::Modules
supplying no import args would make it output $VERSION from every package it
can find.
Michael G Schwern wrote:
I was asked to give something about testing to an audience of undergraduate
informatics students, largely Haskell and maybe some Java. What I finally
came up with is this:
http://www.pobox.com/~schwern/talks/Why_Test/
Liked the emphasis on version control. Had to learn
Ofer Nave wrote:
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
Renaming thread since only the OP referred to Test::Output.
It occurs to me that the Test::* and ExtUtils::* modules should be the
first stop for the Phalanx project. :)
At least as originally proposed by project
Kevin Scaldeferri wrote:
Anyone seen this message with Readonly running under Devel::Cover:
Invalid tie at (eval
22)[/usr/local/lib/perl5/site_perl/5.8.0/Readonly.pm:338] line 9
It's a little spooky... my tests used to be fine, but then I made a
couple innocuous changes in one test file
Walter Goulet wrote:
Looks like the phalanx kwiki as well as the phalanx subversion
repository is down.
Any ETA on when it will be back up?
I can get the repository but not the kwiki. But, IIRC, the kwiki is
hosted by Ingy and is physically independent of the repository, which I
believe is
How do you test that a variable has been tied to a class?
I looked through Test::More; the term 'tie' is conspicuous by its
absence. I also searched the archives of this list and couldn't locate
anything.
I'm looking for something along the lines of Test::More::isa_ok that we
could use like
James E Keenan wrote:
How do you test that a variable has been tied to a class?
I looked through Test::More; the term 'tie' is conspicuous by its
absence. I also searched the archives of this list and couldn't locate
anything.
I'm looking for something along the lines of Test::More::isa_ok
Michael G Schwern wrote:
tie() always returns an object.
The object returned by the new method is also
returned by the tie function, which would be useful if you
want to access other methods in CLASSNAME.
Your insight's and Kevin's were incorporated
Fergal Daly wrote:
Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in
http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm
F
http://search.cpan.org/grep?release=Test-Harness-2.48string=TEST_VERBOSEn=1
HTH
jimk
Dhevendran K wrote:
Hi,
When I am building PERL 5.6.1 on Linux 2.6 Kernel AMD 64 bit machine [i.e.
SUSE LINUX Enterprise Server 9 (x86_64) - Kernel 2.6.5-7.97-default (1) ],
I am getting the following errors.
[snip]
lib/io_multihomedInvalid argument at lib/io_multihomed.t line 108.
Leif Eriksen wrote:
Can this be right ? I checked out DBD-mysql-2.9007 and ran it through
Devel::Cover. Apart from skipping 15 tests to do with leaks and 1 test
to do with transactions, the overall coverage figure from Devel::Cover
is 56%
All tests successful, 1 test and 14 subtests skipped.
Vsevolod Ilyushchenko wrote:
Hi,
I'd like to suggest a module that I came up with to test CGI file
uploading logic.
I have little experience with file uploads via CGI.pm, so let me pose
some questions on more peripheral aspects of your proposal.
test in what sense? Is this supposed to
Kevin Scaldeferri wrote:
I'm looking at a bit of output from Devel::Cover that I imagine has to
be a bug. I'll try my best to reproduce the HTML output:
stmt branch cond sub time code
221862 100 100 _1613639 next if ($line
=~
On Monday, June 27, Marc Prewitt and I will be making a presentation at
YAPC::NA::2005 in Toronto entitled Phalanx from the Trenches: A Local
Perl Users Group's Experience.
While the main focus of our talk will be on our experience with the Perl
Seminar NY Phalanx contingent's work on
Nik Clayton wrote:
All,
There seems to have been a change in the output format for test
failures semi-recently.
Given this test script:
#!/usr/bin/perl
use Test::Harness 0.48;
use Test::More 0.60;
plan tests = 2;
ok(1, 'test 1');
ok(0, 'test 2');
I get this
GlennH wrote:
Hello folks,
I read about the Phalanx project on the yahoo Agile Testing group and
thought I'd sign up the mailing list and skulk in the background.
Don't just skulk. Enlist!
http://qa.perl.org/phalanx/
http://phalanx.kwiki.org/
jimk
Kevin Scaldeferri wrote:
It seems to me like the time Devel::Cover takes to do its book-keeping
when a process terminates is linear in the total number of files in the
cover_db, rather than linear in the number of files involved in that
particular process.
[snip]
This seems unfortunate for
Nik Clayton wrote:
As I write my first set of Test::Builder based tests I'm looking for a
way to test the tests themselves, and make sure that they're doing the
right thing.
A quick peruse of CPAN has thrown up Test::Builder::Tester and
Test::Tester.
I've seen quite a few modules that use
Paul Johnson wrote:
As someone whose production code is currently required to run under
5.5.3, I'm very grateful to module authors whose code still runs under
that version at least. A number of modules which don't run under 5.5.3
do with simple changes, primarily changing our to use vars and
Michael G Schwern wrote:
That said, here's the main differences:
Thanks. My modules are sufficiently non-evil that I should be able to
compensate for these differences.
jimk
I am having trouble figuring out how to test a Perl script which
functions as a command-line utility and which is included with a
CPAN-style distribution.
For purpose of discussion, let's call the distribution XYZ and the
script xyz.pl. My distribution has the following standard structure:
Michael G Schwern wrote:
Make sure MakeMaker is told about that script via EXE_FILES or it won't know
to do anything with it (like install it).
Check. In Makefile.PL, I already had:
EXE_FILES= [
'scripts/modulemaker',
],
[snip]
Michael G Schwern wrote:
Oh yeah, forgot about that. Its not in your path so you have to give it
the full path to the program.
The directories in blib have no relation to where the file came from.
Non-binary executables always go into blib/script. Binary executables
go into blib/bin.
Michael G Schwern wrote:
The other examples in the ticket play out the same way:
bless {}, ref $class || $class;
I encountered the coverage problem inherent in this code in the
constructor of a module whose maintenance I recently assumed. (For that
matter, I could have
James E Keenan wrote:
Michael G Schwern wrote:
Oh yeah, forgot about that. Its not in your path so you have to give
it the full path to the program.
The directories in blib have no relation to where the file came from.
Non-binary executables always go into blib/script. Binary
It's not unheard of for module authors to complain that the automated
test reports posted on testers.cpan.org FAIL modules that ought to PASS.
Tonight, I wish to make the opposite complaint: that one of my own
modules garnered four PASSes when it should have FAILed!
Je m'accuse: Two days
Michael G Schwern wrote:
http://testers.cpan.org/show/Test-Simple.html
Looking at the CPAN tester results for Test-Simple... why are they
suddenly oldest version first? I care about test results from the newest
version, not the oldest.
From personal e-mail:
On Jul 9, 2005, at 8:49 PM,
Ovid wrote:
X-Posted to Perlmonks (http://perlmonks.org/index.pl?node_id=483100)
I frequently write code that generates anonymous functions on the fly.
However, I often want to verify that these functions are correct
without executing them. To this end, I've started writing Test::Code.
Ricardo SIGNES wrote:
* Christopher H. Laco [EMAIL PROTECTED] [2005-09-15T08:23:57]
Would this look for Change OR ChangeLog?
Both seem to be popular on CPAN.
...and some modules have a HISTORY or CHANGES section of POD, and DBI
has DBI::Changes.
Good point. Modules created with
Comrade Burnout wrote:
James E Keenan wrote:
Comrade Burnout wrote:
I'm not sure this is the right place to ask, but I'm at the end of my
rope here.
perl Makefile.pl
make
make test VERBOSE=1
Did you include 'make' between 'perl Makefile.PL' and 'make test'?
yes, i did. i
Comrade Burnout wrote:
James E Keenan wrote:
And, again, to rule out obvious problems ...
1. When you ran 'make', did you get output that looks more or less
like this:
FWIW, here's the full output of make ...
[ burnt ] :: make
cp lib/ExtUtils/ModuleMaker/StandardText.pm
blib/lib
Michael G Schwern wrote:
On Mon, Sep 19, 2005 at 09:42:52PM -0400, James E Keenan wrote:
Schwern: Do you think it's worthwhile accounting for this MakeMaker
anachronism in writing test files, i.e., providing an absolute path to
every chdir call?
I think you misunderstand. The problem
David Landgren wrote:
demerphq wrote:
You miss my point. Whether the code be cross-platform or cross-version,
you need to aggregate the coverage results from all the environments
your code is designed to run on.
How is this done?
David Landgren wrote:
Fergal Daly wrote:
http://www.nntp.perl.org/group/perl.cpan.testers/257538
shows a fail for Test-Benchmark but the fail seems to be caused by
CPANPLUS not installing dependencies:
Apparently it's a bug in CPANPLUS that stops it from keeping track of
grand children
When I began to write this posting, it was to get an answer to a
question. But I figured out a workaround halfway through, so now I'm
posting an answer.
I have happily been using Devel::Cover for more than a year on Perl
5.8.4 on Darwin (Mac OS X 10.3). Recently I upgraded to Perl 5.8.7.
Rob Bloodgood wrote:
Adam Kennedy wrote:
Doesn't makemaker only like you if you have a single .pm file just in
the root directory?
And otherwise you have to have your lib files actually under lib?
lib/Tree/Splay.pm
lib/Tree/Splay/Node.pm
lib/Tree/Splay/IntRange.pm
t/01_basics.t
t/02_compat.t
I would like to report a problem I encountered using Devel::Cover today
and how I got around it.
In preparation for CPAN uploads, I was using Devel::Cover v0.55 on Perl
5.8.7 to do coverage analysis of two different modules I maintain. One
of these modules, Data::Presenter, has been under
Scott Wang wrote:
Hi Chris,
I am still confus.
For example,
On my Linux box, I have a module /tmp/experiment/lib/module_to_test.pm to be tested, and I have two Perl
unit test scripts /tmp/experiment/tests/test1.pl and '/tmp/experiment/tests/test2.pl to load
the module_to_test.pm module and
David Golden wrote:
Dear Michael and Perl QA colleagues,
Wes Barris was trying to install one of my modules and encountered a
dependency problem when Test-Simple-0.62 failed to make on his system.
I was able to get some additional details, but I'm not sure what advice
to offer him. The
Steve Peters wrote:
*http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2001-04/msg01223.html
I wasn't reading perl-qa or any of the other lists on which this
challenge was posted back in 2001. So I was completely unaware of it
until now.
Perhaps, in the perfect wisdom of hindsight,
Yitzchak Scott-Thoennes wrote:
I remember working with some module that had tests something like:
use Test::More;
plan tests = numtests();
...
is($foo, $bar, 'foo is bar');
sub numtests { 13 }
So that when you added a new test to the bottom, the number to modify
was right there
David H. Adler wrote:
Tests pass. One not numeric warning:
t/00compile.ok 1/6Argument 2.57_06 isn't numeric in subroutine
entry at t/lib/Test/More.pm line 670
This is the same warning I reported in an earlier message:
http://groups.google.com/group/perl.qa/msg/fee69dde25cf42ec
Michael G Schwern wrote:
There's other issues with this code. For one, its not portable. You're
using a system command (touch) and you're assuming Unix filepath syntax.
Another is your errors do not include $! which is the reason the command
failed (no such file or directory).
Scott Wang wrote:
We are trying to use Devel::Cover module and cover
in our regression tests run to generate product code
coverage data. However, we met two big problems:
(1) Lots of our perl test scripts failed in code
coverage run and seems related to B::Deparse and we
got million lines of
Scott Wang wrote:
Hi James,
Any information on, generally, how and why
Devel::Cover use B::Deparse module?
Google is your friend. I recommend going to Google Groups and searching
the archives for perl.qa for B::Deparse.
I saw tons of
messages Deep recursion on subroutine
Steffen Mueller wrote:
You
can find a complete (and somewhat current) list of problematic modules
at http://steffen-mueller.net/mi_old.html
Thank you very much for this public service!
jimk
Paul Johnson wrote:
On Tuesday the first [insert desired time period here] Devel::Cover hackathon
was held at the hacker kitchen (aka clkao's flat), sponsored by Best
Practical.
[snip]
So all in all, a very productive and enjoyable day. Lots and lots of thanks
to everyone.
Productive
Ovid wrote:
That appears to be someone trying to install Catalyst and a completely
unrelated failure is being reported in Sub::Override, one of my modules. At
least that's what I *think* the output is saying. Heck, the reason the bug
shows up isn't because Catalyst is trying to use
chromatic wrote:
I have a vim macro to toggle the counter between 'no_plan' and a number.
Could you share that with us? (Adding to new macros to .vimrc is where
I'm *really* Lazy.)
Thanks.
jimk
chromatic wrote:
map ,ton ESC:%s/More tests =/More 'no_plan'; # tests =/CR
map ,toff ESC:%s/More 'no_plan'; # /More /CR$b
My standard just-created test file has the line:
use Test::More 'no_plan'; # tests = 1;
Then I use ,toff and ,ton as necessary. ,toff also puts
A. Pagaltzis wrote:
Hi all,
I just got a failure report [1] on one of my modules that I don’t
know how to read correctly. There’s only one line pertaining to
an error of any sort, and it only mentions the type of error, but
not where or how it happened. What I’d like to know first and
foremost
chromatic wrote:
the Star Trek: Generations
fallacy. You steal a spaceship, which flies through space, to fly through
space to a planet, flying through space, where a temporal anomaly, which also
flies through space, deflected by a supernova, which you flew through space
in your spaceship
What with all the activity on this list in the last week (TAPx::Parser
about to morph into Test::Harness), it's all been more than I can keep
up with.
I would like to suggest that one or more or the hackerati who are
working on all these revisions to our core testing functionality write
an
Mike Malony wrote:
I'm into testing, got some nice .t files, and prove tells me things I'd
rather not hear. So, my next step on the straight and narrow path of
testing, is to gauge my testing coverage.
IN the doc, the synopsis suggests
perl -MDevel::Cover yourprog args
cover
But what can
Adrian Howard wrote:
[snip]
Adrian: How about posting this part on
http://perl-qa.yi.org/index.php/Main_Page?
For more general testing discussions I'd recommend joining all of:
* [EMAIL PROTECTED]
* [EMAIL PROTECTED]
* [EMAIL PROTECTED]
You also might want to look at all or some of:
*
Andy Lester wrote:
On Jun 19, 2007, at 10:52 AM, Mike Malony wrote:
So I'm working my project, and I've got one other more junior coder with
me.
Has anyone tried writing test files as part of their spec's?
An overview document would also be needed, and some time walking
through the
David Golden wrote:
* Module::Starter -- Andy wants these tests run by default and he
doesn't seem to be swayed; So people need to fork this and start
advocating for an alternative. Ditto other module generators. (And
mea culpa for my own.)
You don't need to fork Module::Starter. You
Working on Parrot, I frequently do coverage analysis of the tests I and
others have written for Parrot's configuration and build tools,
components of the project which are written in Perl 5. I display the
results on my server:
James E Keenan wrote:
t/configure/029-option_or_datadubious
Test returned status 0 (wstat 11, 0xb)
after all the subtests completed successfully
I see that the source of this error message is in Test::Harness. But I
don't yet understand why it gets
Gergely Brautigam wrote:
Hi There!
Does anybody know why is that so that sometimes when trying to set a
focuse to a window the window does not come into forground but it stays
on the menubar and just blinks...? Is that a windows problem or a Win32
module problem?
Hi Gergely. Glad to have
Smylers wrote:
James E Keenan writes:
The subject of this thread is Win32::GuiTest -- I know nothing about it,
but given it's a module for use with testing it seems on-topic for this
list.
You are correct. I focused exclusively on the body of the message and
not on the subject. Sorry.
Eric Wilhelm wrote:
Last week was me spending way too much time programming with two hands
behind my back to get 5.5.3 compatibility, bundling Test::More,
creating IO::Capture, etc.
In this package's POD, it would probably be good to distinguish this
package from the IO::Capture
I have had a proposal accepted to do a presentation at the Pittsburgh
Perl Workshop (Oct 13-14) on Better Code via Coverage Analysis during
Testing (http://pghpw.org/ppw2007/talk/725).
During this presentation I hope to:
1. Channel pjcj to the best of my ability.
2. Share some things I've
On Sep 13, 2007, at 2:14 AM, Joshua ben Jore wrote:
Do you know of any addons to the cover program to use information like
this method call site always resolves to the following destinations
or if execution went through this part, what else probably happened?
Sorry, I don't know of any
Michael Carman wrote:
On 9/12/2007 7:41 PM, James E Keenan wrote:
I'd also like to hear any other coverage-related ideas you think would
be worthwhile bringing up at this workshop.
Here's my 2¢
For applications with code in multiple modules use the options for including and
excluding files
On Sep 21, 2007, at 10:35 AM, Paul Johnson wrote:
Actually, the options Michael gave *are* for Devel::Cover itself.
There
are similar (but slightly different - and I hate that) options for
cover.
Well, then, I'm glad I began this thread. While I'm a D::C
enthusiast, I guess my own
James E Keenan wrote:
James E Keenan wrote:
t/configure/029-option_or_datadubious
Test returned status 0 (wstat 11, 0xb)
after all the subtests completed successfully
This problem is maddening because it is intermittent. After not
appearing for more
James E Keenan wrote:
James E Keenan wrote:
James E Keenan wrote:
t/configure/029-option_or_datadubious
Test returned status 0 (wstat 11, 0xb)
after all the subtests completed successfully
I'm still in much the same situation as I was last month. I'll
Let's suppose that I have a suite of test files which I customarily run
with 'prove':
prove t/*.t
... where the tests in t/ are:
alpha.t
beta.t
gamma.t
Let's further suppose that each of these three tests simulates the
operation of a Perl program which is normally called with
Edwardson, Tony wrote:
Anyone written any CPAN modules for which the testing coverage needs to be
improved ?
[snip]
Something from http://qa.perl.org/phalanx/ http://qa.perl.org/phalanx/
would be good
Aspiring hoplites, I salute you! You can read about the adventures of
grizzled
Ovid wrote:
--- Dave Rolsky [EMAIL PROTECTED] wrote:
[snip]
I think there's some truth to this view.
For support I submit this bug ticket -
http://rt.cpan.org/Ticket/Display.html?id=27208
Sorry Dave, but I understand Imacat's point of view. I think part of
the issue is that English is not
Matisse Enzer wrote:
I've spent some of this holiday season learning how to set up BuildBot
(http://buildbot.net/) which is a Continuous Integration system that is
especially aimed at open-source style projects: You set up a central
build master, and one or more build slaves - and it is very
David Cantrell wrote:
On Sat, Dec 29, 2007 at 05:51:50PM -0500, James E Keenan wrote:
If anyone can give me an idiots' guide to how to grab the most recent
source tree, build it, and test it, then I can test it on the same boxes
as I do CPAN testing, plus maybe a couple of others.
svn co
David Cantrell wrote:
On Tue, Jan 01, 2008 at 08:23:52PM -0500, James E Keenan wrote:
David Cantrell wrote:
If anyone can give me an idiots' guide to how to grab the most recent
source tree, build it, and test it, then I can test it on the same boxes
as I do CPAN testing, plus maybe a couple
Thomas Klausner wrote:
which wasn't
proof-read by any english speaking person yet, so if @you want to:
patches welcome ;-)
s/not longer dreadlocked/no longer dreadlocked/
James E Keenan wrote:
I would like to be able to provide the tests run via 'prove' with
options something like this:
some_variant_of_prove t/*.t --option1 --option2 arg1 arg2
... where those 4 command-line options/arguments would be available to
*each* of the individual test files
A couple of points about YAPC::NA:
1. It's almost two weeks earlier this year than it has been in the past
three years. So if your mental clock has been set to 3 days of YAPC +
2 days of hackathon + 3-day 4th-of-July weekend (as mine has), please
reset that clock.
2. Consequentially, the
1. A canned training session, Learn Test::Harness 3.0, that would
provide the user with a guided tour of T::H 3+ and have him/her actually
type and run examples of the new functionality. Canned in the sense
that at a local Perlmongers meeting everyone could download a tarball
and work
Michael G Schwern wrote:
My concern is that we'll be spending time
futzing with git rather than hacking on QA stuff.
We all know SVN/SVK and can stand to use it for a little while longer.
Agreed. One hackathon I attended wasted one-third of the participants'
available time because
If by some chance you run out of things to hack on, you can help out the
Parrot project by taking a look at our smoke testing system --
specifically, its reliance on, and hackish overriding of, two CPAN modules.
Rick Fisk wrote:
Has anyone been successful with producing meaningful coverage reports
when the test files are in a non-standard location?
Any help would be appreciated.
If you make judicious use of the command-line options to cover, as well
as to Devel::Cover's own options, you can
Gabor Szabo wrote:
Should I just use File::Tempdir ?
I haven't yet explored File::Tempdir. But File::Temp has the advantages
of being core, having both functional and OO interfaces, and widely
used. We use it extensively in testing Parrot -- and just tonight I
converted one case where
Paul Fenwick wrote:
G'day QA folks,
Just wanted to report that:
http://cpants.perl.org/
is presently giving me 404 (not found) errors.
Appears fixed as of the time of this message.
Michael G Schwern wrote:
Next step is to get people who want to contribute to the project signed
up as project members. To do this, please send me your Google account
email address.
And a reminder to those who have signed up: When you go to do your
initial 'svn co', the password you
In the attachment, I show several lines from this file coverage report
on a Perl 5 module in the Parrot distribution:
http://thenceforward.net/parrot/coverage/configure-build/config-auto-pmc-pm.html
http://tinyurl.com/5fovnc
Two statements, lines 261-262, each of which is a simple 'push'.
Paul Johnson wrote:
There does seem to be something rather strange going on here. The results for
the unshift a few lines earlier are also duplicated.
Yes, I noticed that after the OP.
But more stragely, the
statement counts on lines 109 and 124 seem somewhat excessive.
My best guess
Paul Johnson wrote:
If you delete all the coverage information and start from
scratch does that solve the problem?
Problem was reproduced:
http://thenceforward.net/parrot/coverage/configure-build/config-auto-pmc-pm.html
At
http://thenceforward.net/parrot/coverage/configure-build/coverage.html I
have for over a year displayed the results of coverage analysis on
Parrot's configuration and build tools.
I have come to realize that while these reports are very useful for me
as the maintainer of the Perl 5 aspect
1 - 100 of 162 matches
Mail list logo
