harder before declaring something unreachable.
Note that this shouldn't be construed as saying that you should create
insane tests, just to get 100% coverage. My point is almost the exact
oppisate: that it's not reasonable to try for 100% conditional coverage.
-=- James Mastros
Rocco Caputo wrote:
On Sun, Jul 11, 2004 at 10:09:38PM +0200, James Mastros wrote:
All unreachable code is either people misusing the term "unreachable", a
bug in Devel::Cover, or dead code that should be removed.
Here's a puzzle, then.
I just ran into a similar "problem&qu
ertations, and attempt to verify each of them using
non-modifying SQL and/or using DBI's standard introspection mechinsimis.
(Hint: One way to get a list of columns in a table is to select * limit
1 from it, and inspect what you get back.)
-=- James Mastros
impurtnce?) has a very low ratio -- but nobody
cares if it lives or dies.)
BTW, what's $report->{files}{ninja}?
A standalone tester would be very nice -- so authors can test their
kwalitee before they upload, rather then after.
There's a couple of misspelled fields in the kwalitee report.
-=- James Mastros
