Lines Matching refs:tests
58 use Test::More tests => $Num_Tests;
117 B<STOP!> If you're just getting started writing tests, have a look at
123 facilities to skip tests, test future features and compare complicated
131 how many tests your script is going to run to protect against premature
136 use Test::More tests => $Num_Tests;
138 There are rare cases when you will not know beforehand how many tests
159 use Test::More tests => 23, import => ['!fail'];
162 have to calculate the number of tests.
165 plan tests => keys %Stuff * 3;
167 or for deciding between running the tests at all:
174 plan tests => 42;
278 ok( $p->tests == 4, 'saw tests' );
604 Sometimes you just want to say that the tests have passed. Usually
656 Test::More. C<use Test::More tests => 1, 'no_diag'>. This is useful
675 =head2 Module tests
813 =head2 Conditional tests
819 necessary to skip tests, or declare that they are supposed to fail
822 For more details on the mechanics of skip and todo tests see
826 block of tests which can be skipped over or made todo. It's best if I
839 This declares a block of tests that might be skipped, $how_many tests
857 which Test::Harness interprets as skipped, but passing, tests.
859 It's important that $how_many accurately reflects the number of tests
860 in the SKIP block so the # of tests run will match up with your plan.
866 You don't skip tests which are failing because there's a bug in your
878 _carp "skip() needs to know \$how_many tests are in the block"
900 Declares a block of tests you expect to fail and $why. Perhaps it's
914 With a todo block, the tests inside are expected to fail. Test::More
915 will run the tests normally, but print out special flags indicating
921 The nice part about todo tests, as opposed to simply commenting out a
922 block of tests, is it's like having a programmatic todo list. You know
929 B<NOTE>: TODO tests require a Test::Harness upgrade else it will
941 With todo tests, it's best to have the tests actually run. That way
945 cases you have no choice but to skip over the broken tests entirely.
948 tests will be marked as failing but todo. Test::Harness will
958 _carp "todo_skip() needs to know \$how_many tests are in the block"
980 but want to put tests in your testing script (always a good idea).
1294 If you simply want to do a little tweaking of how the tests behave,
1317 If all your tests passed, Test::Builder will exit with zero (which is
1319 you run less (or more) tests than you planned, the missing (or extras)
1320 will be considered failures. If no tests were ever run Test::Builder
1322 having successfully completed all its tests, it will still be
1327 0 all tests successful
1331 If you fail more than 254 tests, it will be reported as 254.
1348 bare strings your tests won't notice the difference. This is good.
1373 you're going to distribute tests that use no_plan or todo your
1375 CPAN. If you avoid no_plan and TODO tests, the stock Test::Harness
1401 some tests. You can upgrade to Test::More later (it's forward