On Jul 9, 2004, at 6:06 PM, Andy Lester wrote:
Don't be mesmerized by 100% coverage.
Agreed 100% here. However, I stand by my original statement that you
CAN have 100% coverage on subroutines and pod. Any disagreement on that
one?
I agree with having 100% on subroutines, and I would add that 100% on statements should be a (reasonable) goal too. For my own modules, I usually shoot for 100% statement coverage, which itself implies 100% subroutine, and then I spend a little time trying to squeeze out any extra branch/conditional coverage I can. I will almost always stop (and feel satisfied) if I can get 95+ coverage.
As for POD, in most cases, I agree with you, but to say you should have 100% POD coverage brings up several other questions, such as; Should I document private methods? What about modules which are meant to be configured in the "use" statement, and have little or no subroutines which are intended for usage outside of the module (which I guess is sort of like private methods, but not)? What about tied modules? It usually would not make sense to document the tie hook routines. So I guess what I am saying is sometimes 100% POD coverage would not make sense, and might actually degrade the quality of the documentation by documenting stuff that really does not need to be documented, and therefore only serves to confuse the reader.
Anyway, just my 2 cents on a Sunday afternoon.
Steve
