"Inline" module testing?

LanX has asked for the wisdom of the Perl Monks concerning the following question:

I came up with the following code for module testing in one file.

(Most probably saw something similar before)

use strict;
use warnings;


package use_test;

sub import {
   local $"=", ";
   warn __PACKAGE__."->import( @_ ) called";
}


BEGIN { $INC{__PACKAGE__.".pm"} = 1 } # mark as loaded



package test;

use use_test 1,2,3;
[download]

prints use_test->import( use_test, 1, 2, 3 ) called at c:/tmp/use_test.pl line 9.

Is there an easier way to do it? :)

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

Comment on "Inline" module testing? Select or Download Code

Replies are listed 'Best First'.
Re: "Inline" module testing? by Arunbear (Prior) on Aug 15, 2017 at 10:35 UTC
I'm reminded of Modules as executable scripts? (also Rescue legacy code with modulinos), which looks similar in some ways to your use case.	[reply]
Re^2: "Inline" module testing? by LanX (Saint) on Aug 15, 2017 at 16:07 UTC
I like and use the modulino concept to run my test suites. > I'm reminded of "Modules as executable scripts?" Because it's the mirrored approach, I want to embed a fake module into a runnable script.pl . But in hindsight it's probably better to use the modulino approach right from the beginning to avoid later migration costs. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^3: "Inline" module testing? by Anonymous Monk on Aug 15, 2017 at 17:21 UTC
Modulinos the evil gimmick? Seriously?	[reply]
Re^4: "Inline" module testing? by LanX (Saint) on Aug 15, 2017 at 17:45 UTC
Re: "Inline" module testing? by Anonymous Monk on Aug 15, 2017 at 00:42 UTC
Hi, I don't understand what you want This is iffy `$INC{__PACKAGE__.".pm"} = 1 ;` better is `$INC{ Module::Load::_to_file(__PACKAGE__) } = __FILE__;` I find this easier `#!/usr/bin/perl -- use strict; use warnings; MeMyselfTestSuite() unless caller ; exit 0; BEGIN { package MeMyself; use Module::Load qw/ /; use Data::Dump qw/ dd /; $INC{ Module::Load::_to_file( __PACKAGE__ ) } = __FILE__; sub import { dd( \@_ , [caller] ); } 1; } sub MeMyselfTestSuite { use Module::Load; load( 'MeMyself', 1,2,3,4 ); }` [download]	[reply] [d/l] [select]
Re^2: "Inline" module testing? by LanX (Saint) on Aug 15, 2017 at 00:59 UTC
Thanks! > I don't understand what you want Maybe the wording "module testing" was to sloppy Real module testing requires a test suite, not a sub at the end of the file. I meant rather "module demonstration" or "proof of concept" testing, where module.pm and user.pl are packed into the same file, like when posting an example on perlmonks. Thank you for the interesting code, but it's significantly un-easier for my case, might help me in other occasions though. Cheers Rolf _{(addicted to the Perl Programming Language and ☆☆☆☆ :) Je suis Charlie!}	[reply]
Re^3: "Inline" module testing? by Anonymous Monk on Aug 15, 2017 at 01:49 UTC
:) I usually type out 'The/Name.pm', but I did find this in my notes `BEGIN { $INC{ do{ (my $name = __PACKAGE__)=~s{(::)\|(\.pm$)}{$1?'/':''} +ge; $name }} = __FILE__; }` [download] And right after that a note about https://metacpan.org/pod/Module::Loaded#$bool-=-mark_as_loaded(-PACKAGE-);	[reply] [d/l]