in reply to When 100% Code Coverage Backfires
Generally when given this scenario, I have used Test::MockModule to override something like Data::Record->records() in your example with results that would fully exercise the code, regardless of whether it would otherwise be triggered in its 'natural state'.
Correct me if I'm wrong, but that's a generally acceptable testing practice, isn't it?
perl -e 'split//,q{john hurl, pest caretaker}and(map{print @_[$_]}(joi +n(q{},map{sprintf(qq{%010u},$_)}(2**2*307*4993,5*101*641*5261,7*59*79 +*36997,13*17*71*45131,3**2*67*89*167*181))=~/\d{2}/g));'
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^2: When 100% Code Coverage Backfires
by Ovid (Cardinal) on Mar 26, 2007 at 13:33 UTC |
In Section
Meditations