On 9/12/07, James E Keenan <[EMAIL PROTECTED]> wrote: > I have had a proposal accepted to do a presentation at the Pittsburgh > Perl Workshop (Oct 13-14) on "Better Code via Coverage Analysis during > Testing" (http://pghpw.org/ppw2007/talk/725). > > During this presentation I hope to: > > 1. Channel pjcj to the best of my ability. > 2. Share some things I've picked up in 3+ years of using Devel::Cover > about improving your testing coverage. > > If (a) you have coverage tricks as in (2) that you've picked up, I'd > like to hear them. > > I'd also like to hear any other coverage-related ideas you think would > be worthwhile bringing up at this workshop.
Do you know of any addons to the cover program to use information like "this method call site always resolves to the following destinations" or "if execution went through this part, what else probably happened?" I ask at least partly because of Runops::Trace. The QA dept at work has started using this to produce minimal sets of input that trigger all "possible" code paths by using the checksum_code_path function. It's a work in progress for them but they're excited about it. It lets them pick the non-redundant couple tens of thousands of inputs out of tens of millions in our server's logs. I've lately been interesting in getting visualizations of the code paths and cover looks like the tool to get me there. It's just a thought, y'know. Josh
