FILTER LOADED CLASSES¶

You can redefine the filtering criteria, that is, decide what classes are picked up and what others are not. You do this simply by subclassing "Test::Class::Load" overriding the is_test_class() method. You might want to do this to only load modules which inherit from "Test::Class", or anything else for that matter.

is_test_class

  $is_test_class = $class->is_test_class( $file, $directory )
    

Returns true if $file in $directory should be considered a test class and be loaded by Test::Class::Load. The default filter simply returns true if $file ends with ".pm"

For example:

  use strict;
  use warnings;
  package My::Loader;
  use base qw( Test::Class::Load );
  # Overriding this selects what test classes
  # are considered by T::C::Load
  sub is_test_class {
      my ( $class, $file, $dir ) = @_;
      # return unless it's a .pm (the default)
      return unless $class->SUPER::is_test_class( $file, $dir );
      # and only allow .pm files with "Good" in their filename
      return $file =~ m{Good};
  }
  1;

CUSTOMIZING TEST RUNS¶

One problem with this style of testing is that you run all of the tests every time you need to test something. If you want to run only one test class, it's problematic. The easy way to do this is to change your helper script by deleting the "runtests" call:

 #!/usr/bin/perl -T
 use strict;
 use warnings;
 use Test::Class::Load 't/tests';

Then, just make sure that all of your test classes inherit from your own base class which runs the tests for you. It might looks something like this:

 package My::Test::Class;
 use strict;
 use warnings;
 use base 'Test::Class';
 INIT { Test::Class->runtests } # here's the magic!
 1;

Then you can run an individual test class by using the "prove" utility, tell it the directory of the test classes and the name of the test package you wish to run:

 prove -lv -It/tests Some::Test::Class

You can even automate this by binding it to a key in "vim":

 noremap ,t  :!prove -lv -It/tests %<CR>

Then you can just type ",t" ('comma', 'tee') and it will run the tests for your test class or the tests for your test script (if you're using a traditional "Test::More" style script).

Of course, you can still run your helper script with "prove", "make test" or "./Build test" to run all of your test classes.

If you do that, you'll have to make sure that the "-I" switches point to your test class directories.