in reply to Re^6: Introspecting function signatures
in thread Introspecting function signatures

My suggestion is to just have the test routine call back into the framework:

sub test_something { my $tempdir = create_tempdir(); # ... }

Then the framework only needs to iterate over the package stash and call all test_* functions. Which leads to a "is this a good idea?" question — this style of testing means that the test routines are included with the main code and will have to be compiled every time the module is loaded. Python reduces this overhead by automatically using its form of B::Bytecode/ByteLoader but Perl does not do that, so this style will add some incremental overhead to all use of any module using it. The traditional Perl style of separate test scripts completely avoids this last problem.