There's a rule of thumb that goes along the lines of "bugs lurk where
many changes are made to the source code", because it's a sign of "we're
just not getting this area right."
Has anyone tried to use checkin/diff info to find areas to focus on for
testing? Anyone tied it to a coverage tool? I seem to remember running
across some sort of visual tool that showed activity but I can't find it
now.
Seems like it would be worthwhile but I haven't done it. Is it?
-Kevin
