Test coverage is 18.4%

Gabor Szabo szabgab at gmail.com
Sat Feb 13 19:14:35 UTC 2010

Personally I don't think adding strictly speaking unit tests to already
existing code makes a lot of sense. At least not in the case of a full
blown application.

I'd rather have more Selenium tests or tests that execute the individual
.cgi scripts on the command line.
I never tried to measure coverage of Selenium tests but maybe that
can be done as well.

Then those tests can be included in the t/ directory as well and executed
on condition.

For new code I'd still write the unit tests.

ps. In companies I would be happy with 30-40% coverage, it is usually
way lower but on CPAN modules I regularly see 70-80% see a few of
them here: http://szabgab.com/coverage/

More information about the developers mailing list