Test2::Require::Fork3p

Usage

    use Test2::Require::Fork;
    ... Code that forks ...

Overview

It is fairly common to write tests that need to fork. Not all systems support forking. This library does the hard work of checking if forking is supported on the current system. If forking is not supported then this will skip all tests and exit true.

Explanation

Checking if the current system supports forking is not simple. Here is an example of how to do it:

    use Config;
    sub CAN_FORK {
        return 1 if $Config{d_fork};
        # Some platforms use ithreads to mimic forking
        return 0 unless $^O eq 'MSWin32' || $^O eq 'NetWare';
        return 0 unless $Config{useithreads};
        return 0 unless $Config{ccflags} =~ /-DPERL_IMPLICIT_SYS/;
        # Threads are not reliable before 5.008001
        return 0 unless $] >= 5.008001;
        # Devel::Cover currently breaks with threads
        return 0 if $INC{'Devel/Cover.pm'};
        return 1;
    }

Duplicating this non-trivial code in all tests that need to fork is error-prone. It is easy to forget bits, or get it wrong. On top of these checks, you also need to tell the harness that no tests should run and why.

Source

The source code repository for Test2-Suite can be found at https://github.com/Test-More/test-more/.

Maintainers

Chad Granum <[email protected]>