Your points on Test::Output are well taken. I was experimenting with that module and did get some results via sterr_is and stdout_is.
The 'is' statement only evaluates a return, so your patterns using Test::Output are much more useful in this context.
What I really need out of the test suite is code coverage. I pulled down your code and ran the tests. I tried to run something like:
I was able to spit out some code coverage numbers. I am going to try spend some time on this path and see I can get it to fly on my test script. But I need to dig in a little more and see if Test::Output aligns with Devel::Cover like I hope it does.$ perl -MDevel::Cover pm_script_testing.pl $ cover
In reply to Re^2: Looking for help for unit tests and code coverage on an existing perl script
by tizatron
in thread Looking for help for unit tests and code coverage on an existing perl script
by tizatron
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |