This is PerlMonks "Mobile"

Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  


in reply to Introspecting function signatures

Please forgive what I feel sure verges on a stupid question...but...

I *think* I have some understanding of what you are typing to do. Although it is right at the farthest edge of understanding... But why do you want to? There are well tested existing Test::Most and Test2::Suite and similar modules. What does this approach to testing achieve that these existing solutions don't?

I thought it was a deliberate part of the design of Perl that the functional code and the tests for it were kept distinct and separate.

Replies are listed 'Best First'.
Re^2: Introspecting function signatures
by szabgab (Priest) on Mar 07, 2021 at 05:43 UTC
    I am not sure where this idea came from, that the python tests are included in the modules. They are all separated in files that are called test_SOMETHING.py.

    As of why is this better, there are a number of things that AFAIK Test::Most does not support - for example

    • running individual, independent test functions (e.g. subtests) on their own
    • having a fixtures that will run before and after each subtest.

    Test2::Suite - as far as I understand it is primarily a new harness and it also provides a front-end similar to the one provided by Test::More world (ok, is, like, subtest, etc.) This module is an alternative front-end using Test2 behind the scenes.