I've developed a similar take on test coverage. We test "library" code heavily with Test::More (mainly integration tests, some unit tests). The utilities and apps we write that call them are tested much more casually. We're a small team, and we find the balance to be reasonable for our environment.
We have been disciplined about writing first the POD, then the tests, then the code. I've had the luxury of a fairly inexperienced guy on the team, so I've not been having to fight years of experience, at least with him... The poor guy thinks this is normal.
I've said it before, but I have found the single biggest payoff---even more than writing tests---has been a disciplined approach to consistent POD. Consistently testing has been probably the second most significant gain.
In reply to Re^2: Testing 1...2...3...
by mpeever
in thread Testing 1...2...3...
by raybies
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |