Jeff,
On Nov 5, 2004, at 10:46 AM, Jeff Bisbee wrote:
I'm also curious how other folks run coverage, update modules and rerun coverage.
I tend to not re-make my modules before I test them (then again, they are always pure perl so I don't need to do it as much in a C based module). I have a small shell script (run_coverage.sh) which just removes the cover_db folder, then loops through all the files in t/ and runs them with the command 'perl -MDevel::Cover t/my_test_file.t' and then runs the cover utility. During testing I usually have the coverage.html page open in my browser anyway, so i just refresh it to get the new copy.
Also I was thinking it would be nice to be able to run prove and Devel::Cover together by possibly adding a -M to prove
prove -MDevel::Cover -Ilib -v t/*
I think I might be inclined to agree with Andy that this might not make sense in 'prove'. However, I could see a usefulness for another program which does something like this. Basically it would act like prove (actually be a wrapper around it), but also run coverage at the same time, including doing things like generating the html report as well. I know that would be handy for me (and a lot nicer then the kludgy shell script I am using now). I guess where the question is, what to do with all the output from both prove and Devel::Cover? A nicely formatted combined report would be nice.
Anyway, enough babbling for me, time to get back to work :)
Steve
