Skip Menu |
 

This queue is for tickets about the Kavorka CPAN distribution.

Report information
The Basics
Id: 99115
Status: stalled
Priority: 0/
Queue: Kavorka

People
Owner: Nobody in particular
Requestors: daxim [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 0.034
Fixed in: (no value)



Subject: make Kavorka generated code coverage friendly
Download (untitled) / with headers
text/plain 592b
foo.pl: method foo { return } method bar($something?) { return } method quux(:$file, Bool :$debugging = undef) { return } __PACKAGE__->foo; __PACKAGE__->bar; __PACKAGE__->quux; cover -delete ; perl -MDevel::Cover -MKavorka foo.pl ; cover Coverage should be 100%, but is only 77% because of the extra code generated to handle signatures etc. In a larger project, this extra code is an amount of noise among the test gaps in my own code. So I propose that by default Kavorka should annotate its generated code to exclude it from coverage: http://p3rl.org/Devel::Cover#UNCOVERABLE-CRITERIA
Download (untitled) / with headers
text/plain 163b
Inserting comments is problematic. Perl comments are terminated with a line break. Inserting line breaks screws up the line numbers in error messages and warnings.
Download (untitled) / with headers
text/plain 224b
Is it not possible to achieve 100% coverage by testing the variety of signatures accepted? IMO this is how coverage should be working anyway though I suppose it is technically testing Kavorka rather than the code in question


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.