• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /netgear-R7000-V1.0.7.12_1.2.5/ap/gpl/timemachine/db-4.7.25.NC/perl/BerkeleyDB/t/Test/

Lines Matching defs:More

1 package Test::More;
54 Test::More - yet another framework for writing test scripts
58 use Test::More tests => $Num_Tests;
60 use Test::More qw(no_plan);
62 use Test::More skip_all => $reason;
109 my @status = Test::More::status;
134 The preferred way to do this is to declare a plan when you C<use Test::More>.
136 use Test::More tests => $Num_Tests;
142 use Test::More qw(no_plan);
149 use Test::More skip_all => $skip_reason;
155 If you want to control what functions Test::More will export, you
159 use Test::More tests => 23, import => ['!fail'];
164 use Test::More;
169 use Test::More;
656 Test::More. C<use Test::More tests => 1, 'no_diag'>. This is useful
825 The way Test::More handles this is with a named block. Basically, a
856 code I<won't be run at all>. Test::More will output special ok's
864 the label C<SKIP>, or Test::More can't work its magic.
914 With a todo block, the tests inside are expected to fail. Test::More
989 instances, Test::More provides a handful of useful functions.
1286 =head2 Extending and Embedding Test::More
1288 Sometimes the Test::More interface isn't quite enough. Fortunately,
1289 Test::More is built on top of Test::Builder which provides a single,
1301 my $test_builder = Test::More->builder;
1303 Returns the Test::Builder object underlying Test::More for you to play
1340 Test::More works with Perls as old as 5.004_05.
1346 Test::More from piercing an object's interface allowing better blackbox
1358 Test::More will only be aware of threads if "use threads" has been done
1359 I<before> Test::More is loaded. This is ok:
1362 use Test::More;
1366 use Test::More
1378 Installing Test::More should also upgrade Test::Harness.
1401 some tests. You can upgrade to Test::More later (it's forward
1411 And it plays well with Test::More.