use strict; use warnings; package Test::Class::Load; use Test::Class; use File::Find; use File::Spec; our $VERSION = '0.35'; # Override to get your own filter sub is_test_class { my ( $class, $file, $dir ) = @_; # By default, we only care about .pm files if ($file =~ /\.pm$/) { return 1; } return; } my %Added_to_INC; sub _load { my ( $class, $file, $dir ) = @_; $file =~ s{\.pm$}{}; # remove .pm extension $file =~ s{\\}{/}g; # to make win32 happy $dir =~ s{\\}{/}g; # to make win32 happy $file =~ s/^$dir//; my $_package = join '::' => grep $_ => File::Spec->splitdir( $file ); # untaint that puppy! my ( $package ) = $_package =~ /^([[:word:]]+(?:::[[:word:]]+)*)$/; # Filter out bad classes (mainly this means things in .svn and similar) return unless defined $package; unshift @INC => $dir unless $Added_to_INC{ $dir }++; eval "require $package"; ## no critic die $@ if $@; } sub import { my ( $class, @directories ) = @_; my @test_classes; foreach my $dir ( @directories ) { $dir = File::Spec->catdir( split '/', $dir ); find( { no_chdir => 1, wanted => sub { my @args = ($File::Find::name, $dir); if ($class->is_test_class(@args)) { $class->_load(@args); } }, }, $dir ); } } 1; __END__ =head1 NAME Test::Class::Load - Load C classes automatically. =head1 VERSION Version 0.02 =head1 SYNOPSIS use Test::Class::Load qw(t/tests t/lib); Test::Class->runtests; =head1 EXPORT None. =head1 DESCRIPTION C typically uses a helper script to load the test classes. It often looks something like this: #!/usr/bin/perl -T use strict; use warnings; use lib 't/tests'; use MyTest::Foo; use MyTest::Foo::Bar; use MyTest::Foo::Baz; Test::Class->runtests; This causes a problem, though. When you're writing a test class, it's easy to forget to add it to the helper script. Then you run your huge test suite and see that all tests pass, even though you don't notice that it didn't run your new test class. Or you delete a test class and you forget to remove it from the helper script. C automatically finds and loads your test classes for you. There is no longer a need to list them individually. =head1 BASIC USAGE Using C is as simple as this: #!/usr/bin/perl -T use strict; use warnings; use Test::Class::Load 't/tests'; Test::Class->runtests; That will search through all files in the C directory and automatically load anything which ends in C<.pm>. You should only put test classes in those directories. If you have test classes in more than one directory, that's OK. Just list all of them in the import list. use Test::Class::Load qw< t/customer t/order t/inventory >; Test::Class->runtests; =head1 ADVANCED USAGE Here's some examples of advanced usage of C. =head2 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 C overriding the C method. You might want to do this to only load modules which inherit from C, or anything else for that matter. =over 4 =item B $is_test_class = $class->is_test_class( $file, $directory ) Returns true if C<$file> in C<$directory> should be considered a test class and be loaded by L. The default filter simply returns true if C<$file> ends with C<.pm> =back 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; =head2 CUSTOMIZING TEST RUNS One problem with this style of testing is that you run I 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 C 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 C 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 C: noremap ,t :!prove -lv -It/tests % Then you can just type C<,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 C style script). Of course, you can still run your helper script with C, C or C<./Build test> to run all of your test classes. If you do that, you'll have to make sure that the C<-I> switches point to your test class directories. =head1 SECURITY C is taint safe. Because we're reading the class names from the directory structure, they're marked as tainted when running under taint mode. We use the following ultra-paranoid bit of code to untaint them. Please file a bug report if this is too restrictive. my ($package) = $_package =~ /^([[:word:]]+(?:::[[:word:]]+)*)$/; =head1 AUTHOR Curtis "Ovid" Poe, C<< >> =head1 BUGS Please report any bugs or feature requests to C, or through the web interface at L. I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. =head1 ACKNOWLEDGMENTS Thanks to David Wheeler for the idea and Adrian Howard for C. =head1 COPYRIGHT & LICENSE Copyright 2006 Curtis "Ovid" Poe, all rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.