This is a skeleton of your application to be:

package MyCode;
use strict;
use warnings;

sub run {
    # Main routine here
}

... rest of implementation here...

__PACKAGE__->run() unless caller();
1;
[download]

The "Main program here" section is going to be the code that basically reads the command line options, figures out what to do, and then calls the other subs or methods to make it happen. The "rest of implementation here" is simply placeholder text to indicate where you'd put the code that actually implements getting things done - that is the code your tests would be testing. The "__PACKAGE__..." line is what makes this .pm file into an executable program; it says "if caller() doesn' return anything (that is, we haven't been loaded by someone else as a module), execute this package's run() method."

Here's a contrived example.

package Sample;
use strict;
use warnings;

use GetOpt::Long;

__PACKAGE__->run() unless caller();

sub run {
    my($should_foo);
    die "usage: Sample.pm [--foo|--bar]\n"
        unless(GetOptions('foo' => \$should_foo,
                          'bar' => \$should_bar);
    my $value = $should_foo ? foo() : bar();
    print  $value;
}

sub foo {
    return "Foo to you too\n";
}
sub bar {
    return "The best bar none\n";
}

1;
[download]

Now in you tests, you can do stuff like this:

use Test::More tests=>1;
use Test::Exception;

use Sample;
is Sample->bar(), "The best bar none\n", 'bar() works';
is Sample->foo(), "Foo to you too\n", 'foo() works';

local @ARGV; # now undef
dies_ok { Sample->run() } 'no args dies as expected';
like $@, qr/^usage:/, 'got a usage message';
[download]

(Note that I have not tested this; it is simply meant to be an illustration of technique.)

You package has subs that can be tested now to see if they do what they are supposed to. I hope this points you toward a workable direction.

Edit: Not sure why this is getting down voted - would someone care to comment? Do you disagree with the technique? Do you feel I should have solved the problem more completely? Actual feedback is more useful.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.