> Teach the other folks how to test. :)
The journey of a thousand miles begins with a single step, and in this
case the single step is making it terribly obvious to me as the lead tech
that their code doesn't compile properly. :-)
> sub test {
> return unless /\.pm$/;
> print
On Thu, Apr 11, 2002 at 02:49:30PM -0500, Andy Lester wrote:
> > One simple way around this is to use SelfTest or Test::Inline and
> > throw in at the top of each of your modules:
> >
> > =for testing
> > use_ok('My::Self');
> >
> > and then just run the tests in each self-testing module i
> One simple way around this is to use SelfTest or Test::Inline and
> throw in at the top of each of your modules:
>
> =for testing
> use_ok('My::Self');
>
> and then just run the tests in each self-testing module in turn.
The bummer is that I'm not the only programmer, and I've had probl
On Thu, Apr 11, 2002 at 12:16:27PM -0500, Andy Lester wrote:
>
> I'm using Test::More for doing infrastructure testing throughout my
> project. One of the tests I'm doing is making sure that every .pm file is
> able to load on its own, since I've had problems where the .pm had
> dependencies on
