| Name : perl-Test-Inspector
| |
| Version : 0.03
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : lp154.6.1
| Date : 2023-01-27 17:38:21
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Test-Inspector-0.03-lp154.6.1.src.rpm
|
| Size : 0.01 MB
| |
| Packager : https://www_suse_com/
| |
| Summary : are you testing everything?
|
Description :
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\'. Y\'see?
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-T/15.4/noarch |
