Good links there. Appreciate it.

In this theme, I went ahead and tried to setup an env similar to the layout described in this link:

StackOverFlow Complete build/unittest/codecoverage

couple of things that I did:

• Created the layout described. Made directories for 'lib' and 't'.
• Copied my script to lib. Flipped the extension to pm. Added a package statement to the script. Also added: __PACKAGE__->main( @ARGV ) unless caller();
• Wrapped the main block of code, what I called the implied main, in sub main{...}

Then I was able to add a stanza to my test file.

my $my_dev_1 = sample::main("my-dev-1");
is($my_dev_1, "---
classes:
  - all
  - dev
", "my dev 1 test");
[download]

Not sure how I feel about the sample::main("my-dev-1"). Would appreciate some feedback on that to see if I am calling this correctly.

That said, I was able to generate code cover from this setup.

$ ./Build test
$ ./Build testcover

---------------------------- ------ ------ ------ ------ ------ ------ ------
File                           stmt   bran   cond    sub    pod   time  total
---------------------------- ------ ------ ------ ------ ------ ------ ------
blib/lib/sample.pm             97.4   91.7    n/a  100.0    0.0  100.0   93.2
Total                          97.4   91.7    n/a  100.0    0.0  100.0   93.2
---------------------------- ------ ------ ------ ------ ------ ------ ------

That processes pumps out a cover.html file that kinda aligns more with what I was hoping to see. The changes to the original code are not significant, but they are changes, more than what I was hoping to make, perhaps digging in harder on Test::Output would help.