* Stevan Little ([EMAIL PROTECTED]) wrote: > 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.
Well well I'm testing in retrospect using the coverage reports as the driving factor. And I've found that the 'make test' step doesn't look in the 'lib' directory, but in the blib directory and I need to 'remake' the module if I make any changes to the code itself (and not the tests) I was just wondering if there was an easier way where make test whould like in lib and not blib. -- Jeff Bisbee / [EMAIL PROTECTED] / jbisbee.com
