headers
Spiros Denaxas | 19 Sep 12:16
Gravatar

code coverage metrics

Hello,

I recently sent Chris an email about an idea I had, quantifying (and
improving) the test coverage that we currently have on the bioperl
core. I know there's a list on the wiki [1] with a list of tests that
have low coverage and/or complete lack of tests. My idea was to
somehow standardize and automate the generation of this list,
preferably on a weekly basis initially. We can then more easily see
where help is needed and possible assign individual tasks to tackle
the most-suffering modules.

There are currently several very good CPAN modules that do this, like
Devel::Cover [2]. Is there any objection if I kick this off and start
doing some work, aiming into creating a more detailed report on code
coverage using the current HEAD and test suite?

Spiros

[1] http://www.bioperl.org/wiki/Untested_Modules_in_BioPerl
[2] http://search.cpan.org/dist/Devel-Cover/lib/Devel/Cover.pm
Permalink | Reply |
headers
Sendu Bala | 19 Sep 13:49
Favicon

Re: code coverage metrics

Spiros Denaxas wrote:
> There are currently several very good CPAN modules that do this, like
> Devel::Cover [2]. Is there any objection if I kick this off and start
> doing some work, aiming into creating a more detailed report on code
> coverage using the current HEAD and test suite?

You should read our previous discussion here:
http://thread.gmane.org/gmane.comp.lang.perl.bio.general/14586/focus=14588

Basically I think we have it all in place now; someone just needs to 
take that last step and run a cron job that runs the Build commands. We 
also need the website side of things sorted out I think.

If you could make those things happen and take care of any issues that 
crop up, that would be great.
Permalink | Reply |
headers
Spiros Denaxas | 19 Sep 13:51
Gravatar

Re: code coverage metrics

On Fri, Sep 19, 2008 at 12:49 PM, Sendu Bala <bix <at> sendu.me.uk> wrote:
> Spiros Denaxas wrote:
>>
>> There are currently several very good CPAN modules that do this, like
>> Devel::Cover [2]. Is there any objection if I kick this off and start
>> doing some work, aiming into creating a more detailed report on code
>> coverage using the current HEAD and test suite?
>
> You should read our previous discussion here:
> http://thread.gmane.org/gmane.comp.lang.perl.bio.general/14586/focus=14588
>
> Basically I think we have it all in place now; someone just needs to take
> that last step and run a cron job that runs the Build commands. We also need
> the website side of things sorted out I think.
>
> If you could make those things happen and take care of any issues that crop
> up, that would be great.
>

Enlightening, thank you for pointing that out. I will have a look, I
don't see a problem with the plan.

Spiros
Permalink | Reply |
headers
Spiros Denaxas | 19 Sep 14:01
Gravatar

Re: code coverage metrics

>
> Enlightening, thank you for pointing that out. I will have a look, I
> don't see a problem with the plan.
>
> Spiros
>

I have also updated the wiki to make sure we avoid duplicate effort on
this, http://www.bioperl.org/wiki/Project_priority_list

Spiros
Permalink | Reply |
headers
Chris Fields | 19 Sep 14:22
Gravatar

Re: code coverage metrics


On Sep 19, 2008, at 6:51 AM, Spiros Denaxas wrote:

> On Fri, Sep 19, 2008 at 12:49 PM, Sendu Bala <bix <at> sendu.me.uk> wrote:
>> Spiros Denaxas wrote:
>>>
>>> There are currently several very good CPAN modules that do this,  
>>> like
>>> Devel::Cover [2]. Is there any objection if I kick this off and  
>>> start
>>> doing some work, aiming into creating a more detailed report on code
>>> coverage using the current HEAD and test suite?
>>
>> You should read our previous discussion here:
>> http://thread.gmane.org/gmane.comp.lang.perl.bio.general/14586/focus=14588
>>
>> Basically I think we have it all in place now; someone just needs  
>> to take
>> that last step and run a cron job that runs the Build commands. We  
>> also need
>> the website side of things sorted out I think.
>>
>> If you could make those things happen and take care of any issues  
>> that crop
>> up, that would be great.
>>
>
> Enlightening, thank you for pointing that out. I will have a look, I
> don't see a problem with the plan.
>
(Continue reading)

Permalink | Reply |
headers
Mauricio Herrera Cuadra | 19 Sep 16:06

Re: code coverage metrics

Sorry guys, this has been my fault due to lack of time. I have a very 
old ticket waiting for me at the OBF Helpdesk to get the website side of 
things done. Spiros, I have some spare time today to try setting it up, 
assign it to me in the wiki list if you want, I'll send an update in a 
couple of days.

Thanks,
Mauricio.

Chris Fields wrote:
> 
> On Sep 19, 2008, at 6:51 AM, Spiros Denaxas wrote:
> 
>> On Fri, Sep 19, 2008 at 12:49 PM, Sendu Bala <bix <at> sendu.me.uk> wrote:
>>> Spiros Denaxas wrote:
>>>>
>>>> There are currently several very good CPAN modules that do this, like
>>>> Devel::Cover [2]. Is there any objection if I kick this off and start
>>>> doing some work, aiming into creating a more detailed report on code
>>>> coverage using the current HEAD and test suite?
>>>
>>> You should read our previous discussion here:
>>> http://thread.gmane.org/gmane.comp.lang.perl.bio.general/14586/focus=14588 
>>>
>>>
>>> Basically I think we have it all in place now; someone just needs to 
>>> take
>>> that last step and run a cron job that runs the Build commands. We 
>>> also need
>>> the website side of things sorted out I think.
(Continue reading)

Permalink | Reply |

Gmane