Why does your test suite need to be a module? Almost by definition it needs to be one or more perl scripts that use Parse::FixedLength as the object of the exercise is to test your actual module(s) in the context it/they will be used.
I presume you are using h2xs as recommended to generate your basic module component stubs and directory structure:
C:\>h2xs -X -n Parse::FixedLength Writing Parse/FixedLength/FixedLength.pm Writing Parse/FixedLength/Makefile.PL Writing Parse/FixedLength/test.pl Writing Parse/FixedLength/Changes Writing Parse/FixedLength/MANIFEST C:\>
These stubs contain all the basic files/code for your distro which makes life easier.perlman:perlxstut is not a bad read. It has a C focus but the intro sections are applicable to any module and cover a bit on testing.
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
In reply to Re: Including a 'test only' module in distribution
by tachyon
in thread Including a 'test only' module in distribution
by runrig
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |