--- Adrian Howard <[EMAIL PROTECTED]> wrote:

> * The Perl::Critic tests slowed the T::A tests down. Didn't bother to
 
> figure it out - just swapped it out again. Anybody know why?

I couldn't tell you why, but that reminds me of another thing we'll be
doing to speed up tests.

Tests fall into two categories:  those which can fail and those which
can't.  The former tests are basically about coding standards and other
things which don't really affect how your code runs.  Did you use a
bare return or not (Perl::Critic stuff)?  Did you "use strict"?  Is
your POD well-formed?  Those sorts of tests are probably going to go
into a test/standards/ directory and need to be run during integration
or before merges but don't really need to be run all the time to verify
that your code is doing what it's supposed to be doing.

This should save us more time on our tests.

Cheers,
Ovid

--
Buy the book  - http://www.oreilly.com/catalog/perlhks/
Perl and CGI  - http://users.easystreet.com/ovid/cgi_course/
Personal blog - http://publius-ovidius.livejournal.com/
Tech blog     - http://use.perl.org/~Ovid/journal/

Reply via email to