On Fri, May 08, 2009 at 06:34:39PM +0200, Renee Bäcker wrote:
> Hi,
>
> Anthony Gladdish schrieb:
> > Has anyone else experienced this with Test::TestCoverage, or can anyone
> > tell me if this should be happening and suggest a work around or solution
> > such as "don't use Test::TestCoverage".
>
> As a workaround, you can use this method:
>
> test_coverage_except( $module, @subs );
>
> test_coverage_except( 'DBIC::module', '<relationship>_rs', ... );
>
> If you can send me a small test case, I can work on a better solution.
The problem is simple - we've started using Sub::Name::subname to name up
generated methods so they get correctly recognised as methods in the class
rather than imports.
Once we go to Moose you'll be able to test
$meta_method->isa('Class::MOP::Method::Generated')
to exclude. But that's not true yet. Suggestions very much welcome.
--
Matt S Trout Catalyst and DBIx::Class consultancy with a clue
Technical Director and a commit bit: http://shadowcat.co.uk/catalyst/
Shadowcat Systems Limited
mst (@) shadowcat.co.uk http://shadowcat.co.uk/blog/matt-s-trout/
_______________________________________________
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
