Test2¶

Test2 supports forking. For forking to work you need to load Test2::IPC.

Test::Builder¶

Test::Builder Did not used to support forking, but now that it is based on Test2 it does. Test2::IPC must be loaded just as with Test2.

Test2::Suite¶

Test2::Suite tools should all work fine with true forking unless otherwise noted. Pseudo-fork via threads (Windows and a few others) is not supported, but may work.

Patches will be accepted to repair any pseudo-fork issues, but for these to be used or tested they must be requested. Fork tests should not run on pseudo-fork systems unless they are requested with an environment var, or the AUTHOR_TESTING var. Pseudo-fork is fragile, and we do not want to block install due to a pseudo-fork flaw.

Test::SharedFork¶

Test::SharedFork is currently support and maintained, though it is no longer necessary thanks to Test2::IPC. If usage ever drops off then the module may be deprecated, but for now the policy is to not let it break. Currently it simply loads Test2::IPC if it can, and falls back to the old methods on legacy installs.

Others¶

Individual authors are free to support or not support forking as they see fit.

Test2¶

The core of Test2 supports threading so long as Test2::IPC is loaded. Basic threading support (making sure events make it to the parent thread) is fully supported, and must not be broken.

Some times perl installs have broken threads (Some 5.10 versions compiled on newer gcc's will segv by simply starting a thread). This is beyond Test2's control, and not solvable in Test2. That said we strive for basic threading support on perl 5.8.1+.

If Test2 fails for threads on any perl 5.8 or above, and it is reasonably possible for Test2 to work around the issue, it should. (Patches and bug reports welcome).

Test::Builder¶

Test::Builder has had thread support for a long time. With Test2 the mechanism for thread support was switched to Test2::IPC. Test::Builder should still support threads as much as it did before the switch to Test2. Support includes auto-enabling thread support if threads is loaded before Test::Builder.

If there is a deviation between the new and old threading behavior then it is a bug (unless the old behavior itself can be classified as a bug.) Please report (or patch!) any such threading issues.

Test2::Suite¶

Tools in Test2::Suite have minimal threading support. Most of these tools do not care/notice threading and simply work because Test2::IPC handles it. Feel free to report any thread related bugs in Test2::Suite. Be aware though that these tools are not legacy, and have no pre-existing thread support, we reserve the right to refuse adding thread support to them.

Test2::Workflow

Test2::Workflow has been merged into Test2::Suite, so it gets addressed by this policy.

Test2::Workflow has thread support, but you must ask for it. Thread tests for Test2::Workflow do not event run without setting either the AUTHOR_TESTING env var, or the T2_DO_THREAD_TESTS env var.

To use threads with Test2::Workflow you must set the T2_WORKFLOW_USE_THREADS env var.

If you do rely on threads with Test2::Workflow and find a bug please report it, but it will be given an ultra-low priority. Merging patches that fix threading issues will be given normal priority.