![]() |
|
We don't bite newbies here... much | |
PerlMonks |
Devel::Cover and symbolic links -- borked?by DrWhy (Chaplain) |
on Jul 21, 2011 at 22:40 UTC ( [id://916012]=perlquestion: print w/replies, xml ) | Need Help?? |
DrWhy has asked for the wisdom of the Perl Monks concerning the following question:
We have a large application framework here at work that I work on. It's made up of mostly perl scripts and modules (with a mixure of code in other languages, but that's not important now). We have an extensive set of test scripts and want to measure the Perl code coverage. One consequence of the architecture we implemented is that many of the perl scripts are symlinked in multiple locations (each application within the framework has its own code space and code that needs to be shared among different apps is placed in one application's space and symlinked into all the other apps' spaces).
I get what looks like accurate coverage measures out of runs of the full test set for those scripts that are *not* symlinks. For the scripts that are symlinked a few of them seem to give some reasonable coverage data, but most of them show no coverage data at all. They are listed in the HTML report pages, but all usage stats columns, stmt, bran, cond, sub, and time (not doing pod coverage), all say 'n/a'. Some of these scripts are quite large and are surely used many times within the test set but it is essentially reporting 0% coverage which is just not possible. So it looks like the system is getting confused when you run the same script via different paths (via symlinking). Is this a known issue and is there any kind of workaround? In the interest of full disclosure (as much as my company will allow anyway) I did modify Devel::Cover so that it can operate in a parallel grid computing system. Update: typos fixed. --DrWhy "If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."
Back to
Seekers of Perl Wisdom
|
|