# from nadim khemir
# on Sunday 26 October 2008:
>The actual number of tests being the sum of all the tests for the
> module dependencies (including core ones) + my own tests.
Don't forget the perl core tests ;-)
>I also believe that the number of tests per line of code is an
> interresting figure (again, pertinence is not my point).
I would attach some importance to whether or not the tests pertain to
the code you're actually running. If you call one function from a
dependency which has 1000 otherwise irrelevant tests, do you count
those 1000 tests or only the 10 which cover the function you're
calling?
>Do we have a system to gather the test data for all the modules?
Devel::Cover sometimes "leaks" coverage from some other code into the
results, so I suppose the information is being gathered (but typically
filtered) as you traverse the code in your dependencies. So, it seems
possible to intersect coverage data from that module's test suite (and
it would be interesting to know how much the functions/methods you're
calling have been tested.)
Or you could just add the test counts and pretend that complexity
doesn't exist ;-)
--Eric
--
hobgoblin n 1: (folklore) a small grotesque supernatural creature that
makes trouble for human beings
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
