You're missing the point. In the following code sample the child immediately exits without running any tests. In my real tests the child is an artifact of the module code and isn't meant to be tested directly (there's some IPC going on). I should be able to kill off Test::More in the child so it can get on with taking care of its parent without being expected to run tests as well.
use Test::More 'no_plan'; exit unless fork; ok( 1 ); __DATA__ ok 1 # No tests run! 1..1
In reply to Re: Re: Getting Test::More to ignore forked children
by diotalevi
in thread Getting Test::More to ignore forked children
by diotalevi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |