Lines Matching refs:tests

3 Test::Tutorial - A tutorial about writing really basic tests
10 me write tests!>
17 Is this you?  Is writing tests right up there with writing
55     use Test::Simple tests => 1;
66     use Test::Simple tests => 2;
76     # Looks like you failed 1 tests of 2.
78 C<1..2> "I'm going to run two tests."  This number is used to ensure
80 tests.  C<ok 1> "The first test passed."  C<not ok 2> "The second test
82 your tests.
100     use Test::Simple tests => 2;
120 tests you can figure out which one is #2, but what if you have 102?
125     use Test::Simple tests => 2;
145     use Test::Simple tests => 8;
174     # Looks like you failed 1 tests of 8.
196     use Test::More tests => 8;
228     # Looks like you failed 1 tests of 8.
232 when writing up the tests.  Just change it to:
245 =head2 Sometimes the tests are wrong
248 code.  Ergo, tests have bugs.  A failing test could mean a bug in the
265     use Test::More tests => 32;
300 the C<use Test::More tests =E<gt> ##> line.  That can rapidly get
313     # For each key in the hash we're running 8 tests.
314     plan tests => keys %ICal_Dates * 8;
317 running some tests, don't know how many. [6]
319     use Test::More 'no_plan';   # instead of tests => 32
321 now we can just add tests and not have to do all sorts of math to
347 Describe what the tests test, to make debugging a failed test easier
351 =head2 Skipping tests
353 Poking around in the existing Date::ICal tests, I found this in
358     use Test::More tests => 7;
372     # like the tests above, but starting with ical instead of epoch
385     use Test::More tests => 7;
402         # like the tests above, but starting with ical instead of epoch
410 MacOS, all the tests run normally.  But when on MacOS, C<skip()> causes
413 the tests have been skipped.
424 This means your tests won't fail on MacOS.  This means less emails
425 from MacPerl users telling you about failing tests that you know will
426 never work.  You've got to be careful with skip tests.  These are for
427 tests which don't work and I<never will>.  It is not for skipping
430 The tests are wholly and completely skipped. [10]  This will work.
439 =head2 Todo tests
453     use Test::More tests => 1;
467     # Looks like you failed 1 tests of 1.
474     use Test::More tests => 1;
492 Test::More doesn't say "Looks like you failed 1 tests of 1".  That '#
494 failure as a successful test.  So you can write tests even before
511 It's very simple to have your tests run under taint mode.  Just throw
513 in C<#!> and use them to run your tests.
535 some bugs, which is good -- we'll uncover them with our tests.
553 didn't say how many tests we're going to run, how can we know it
581 Do NOT be tempted to use TODO tests as a way to avoid fixing simple