Test::Inspector - are you testing everything?
SYNOPSIS
my $inspector = Test::Inspector->setup({
modules => [ 'Foo::Bar', 'Bar::Baz', ... ],
dirs => [ '/path/to/test/dir1', '/path/to/test/dir2', ... ],
ignore => [ 'import_from_elsewhere_method1', 'also_imported', ... ],
private => 1, # tests *all* methods, don't ignore ones that start _
});
print $inspector->inspect;
Ever been asked to write tests for an unknown codebase? A large codebase, that may, or may not, have tests associated with it? How do you know if you need to test a method? Is it already tested?
This doesn't answer those questions per se. It tries to make a first best stab at it for you.
Supply a list of modules, supply a list of test directories, and we see if the methods in the modules are called anywhere in those directories. It doesn't mean that the tests are good, but it might help you in where to add a new test, or which tests you should be running.
If you import methods into a module, you may not want to know if they are tested by your good self. That should be up to the exporting module's test suite, right? Using the 'ignore' key to the hashref or args, you can say you don't care about those methods. Like, say, in this itself, I use File::Find, but don't really want to be worrying about if I have tested 'find' or 'finddepth'.
Product's homepage
Requirements:
· Perl
Find us on Google+
