On Thu, May 02, 2013 at 12:51:06PM -0700, Karen Etheridge wrote:
> On Thu, May 02, 2013 at 02:39:13PM -0500, brian d foy wrote:
> > In HARNESS_OPTIONS we can set -jN to note we want parallel tests
> > running, but how can a particular module, which might be buried in the
> > dependency chain, tell the harness it can't do that?
> When can a test not be parallelizable?
When you use Test::Class and all your tests inherit this:
sub start_from_a_known_state_because_doing_anything_else_is_stupid
:Test(startup) {
shift()->truncate_all_database_tables();
}
No, you can't have your tests clean up after themselves. For two
reasons. First, that means you have to scatter house-keeping crap all
over your tests. Second, if you have a test failure you want the
results to be sitting there in the database to help with debugging.
--
David Cantrell | even more awesome than a panda-fur coat
All children should be aptitude-tested at an early age and,
if their main or only aptitude is for marketing, drowned.
