Lines Matching refs:in
14 # In case a test is run in a persistent environment.
88 such that their output is in the format that
94 a new file called F<t/test.t> (in a new F<t> directory). If you have
111 This should be the first thing you call in your test script. It
120 These are the things that you can put in the parameters to plan:
126 The number of tests in your script.
144 in a C<BEGIN {...}> block, like so:
181 (chr(65) eq 'A') ? "\n" : " in a non-ASCII world\n";
256 The expression is evaluated in scalar context. So the following will
260 ok( !grep !defined $_, @stuff ); # ok if everything in @stuff is
263 A special case is if the expression is a subroutine reference (in either
309 Finally, you can append an optional third argument, in
397 print $TESTERR "# Failed test $ntest in $context\n";
399 print $TESTERR "# Failed test $ntest in $context: $diag\n";
476 note about why it's being skipped. So in the first codeblock above, read
482 string "Skip", as shown in the above examples.
484 Note that in the above cases, C<thing($foo)> and C<thing($bar)>
528 # We print in one shot for VMSy reasons.
567 are in this category. If a normal test doesn't succeed, then that
583 then the feature in question shouldn't be on the TODO list, now
588 and the newly working feature should be documented in the release
589 notes or in the change log.
612 probably over-kill in most cases. (Your test code should be simpler
653 so easy to make that mistake in reading C<ok @foo, @bar> that you might
691 skipped. But in reality, they I<are> evaluated, but C<skip> just won't
698 But that's not terribly pretty. You may find it simpler or clearer in
712 But be quite sure that C<ok> is called exactly as many times in the
713 first block as C<skip> is called in the second block.
738 L<Test::Inline> and L<SelfTest> let you embed tests in code.