Lines Matching defs:plan
31 plan
110 =head2 I love it when a plan comes together
112 Before anything else, you need a testing plan. This basically declares
116 The preferred way to do this is to declare a plan when you C<use Test::More>.
150 Alternatively, you can use the C<plan()> function. Useful for when you
154 plan tests => keys %Stuff * 3;
160 plan skip_all => 'Test irrelevant on MacOS';
163 plan tests => 42;
168 sub plan {
171 return $tb->plan(@_);
230 the plan when you're done running tests.
232 $number_of_tests is the same as C<plan()>, it's the number of tests you
237 This is safer than and replaces the "no_plan" plan.
240 The plan is there to ensure your test does not exit before testing has
759 C<subtest()> runs the &code as its own little test with its own plan and
770 plan tests => 2;
793 plan skip_all => 'cuz I said so';
799 Due to how subtests work, you may omit a plan if you desire. This adds an
1371 in the SKIP block so the # of tests run will match up with your plan.
1372 If your plan is C<no_plan> $how_many is optional and will default to 1.
1388 # If the plan is set, and is static, then skip needs a count. If the plan
1389 # is 'no_plan' we are fine. As well if plan is undefined then we are
1392 my $plan = $tb->has_plan;
1394 if $plan && $plan =~ m/^\d+$/;