Re: " he is most interested..the vast data sets generated by..successes and failures of
designing a test that covers the largest amount of code in the smallest amount of time is never a bad thing...
unless you define "test" as 'unit testing EVERY possible trivial thing INCLUDING functions that return trivial answers like 1+1 = 2, making sure they STILL return 2, years after being written, without any modifications being done to them'.
/me seen that last part, to some extent. won't go there. waste of time. if you need THAT, test "the library" separately, and only when you CHANGE it.
in any case, there's also "data overload". The solution is to turn data into 'information' rather than 'a bunch of meaningless, uh, data'. then you present the information, executive summary first, with drill-down capability for those who really want that.
Biting the hand that feeds IT
