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 ne
> I will be covering some of these coverage reporting options at PPW. If
> you have actual use cases, please post. Thank you very much.
coverage for xs was really hard for me to figure out... until paul
pointed me toward the gcov2perl manpage, where I learned that
$ cover -test
tool care of
On Fri, Sep 21, 2007 at 05:51:36AM -0400, James E Keenan wrote:
> 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 applicati
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 9/14/2007 3:50 PM, Paul Johnson wrote:
>
> Most of the infrastructure is in place for path coverage, but the data
> isn't collected at the moment.
Ooh, would that provide the data I need to fix the conditional coverage report?
-mjc
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 (-ignore, +inc, -select
On 9/14/07, Paul Johnson <[EMAIL PROTECTED]> wrote:
> I've started on a sort report to provide an optimal test ordering, so
> that you can do the majority of your testing as soon as possible, or
> identify tests which don't add to your coverage, but this isn't finished
> yet.
That's interesting. H
On Thu, Sep 13, 2007 at 06:33:40AM -0400, James E Keenan wrote:
> 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"
I don't collect any informati
Thanks, Paul. As I get closer to the talk, I'll probably have you take a look
at my draft for more comments.
Jim Keenan
On Wed, Sep 12, 2007 at 08:41:22PM -0400, James E Keenan wrote:
> 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).
Congratulations. And it looks like a
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
On 9/12/07, James E Keenan <[EMAIL PROTECTED]> wrote:
> 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. Chan
James E Keenan wrote:
> 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 a
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
14 matches
Mail list logo
