Feature request: optionally tell "ok" module to BAIL_OUT if module cannot be loaded

[XSven]

I am looking for a way to replace this idiom

BEGIN {
  use_ok( 'Some::Module' ) or BAIL_OUT( "Cannot load module 'Some::Module'!" );
}

with something that uses the ok module?!

[exodist]

I think this feature request should be a new module. I do not want to complicate ok.pm with this functionality.

I would suggest subclassing https://metacpan.org/pod/Test2::Require::Module in Test2::Require::ModuleOrBail that implements the additional behavior.

If you write it as a PR against Test2-Suite I will likely merge it. But it is also perfectly reasonable as a stand alone cpan dist.

[briandfoy]

I do this with a subroutine in a module that I share among my tests. Part of that is I want better control of the error reporting, and I already have a utility module for tests to access application specific things they need in a common way. Since I already have that utility module, it's easy to add functions.

Typically I have some other checks besides the use because I've made a lot of dumb errors (Some:Class) that I also want to check. My general strategy in any test is to catch myself being dumb and report the most specific sort of dumbness I can based on my general past idiocy. If I can catch dumb errors before the use, I can make better error messages. It looks something like this:

sub load (@classes) {
    subtest 'sanity' => sub {
        foreach my $class ( @classes ) {
            ok valid_package_name($class), "$class is a valid package name";
            ok file_exists($class), ....;
            use_ok $class;
        }
}

These tests may seem overly targeted, but while developing, sometimes a module name changes because I'm an idiot at naming things and often the team comes up with a better name. Along with that, the module name changes but I forget which tests use that name. Sure, grep could find those, but did I mention how dumb I am (especially in the middle of the night after several hours working on a problem)? :)

Note a drawback I recently had. Things like $TODO are based on the current package, so a $TODO in a subtest in a separate package won't respect the TODO: label in a calling package that is different. Again, completely understandable once I stop being an idiot.

[exodist]

@briandfoy $TODO is essentially deprecated in favor of this from Test2: https://metacpan.org/pod/Test2::Todo it plays nicely with Test::Builder based tools, so you can start using that. Or even the todo() function from https://metacpan.org/pod/Test2::Tools::Basic#$todo-=-todo($reason) Once againm, plays nicely with older tools, and does not suffer from the package variable problem.

[briandfoy]

Indeed Test2 does some things better. But, Test2 was only just recently added to core so the old ways will persist for several more years.