Lines Matching refs:test
54 Test::More - yet another framework for writing test scripts
123 facilities to skip tests, test future features and compare complicated
140 have no plan. (Try to avoid using this as it weakens your test.)
232 By convention, each test is assigned a number in order. This is
234 assign a name to each test. Which would you rather see:
247 to find the test in your script, simply search for "simple
250 All test functions take a name argument. It's optional, but highly
257 ok #" depending on if a given test succeeded or failed. Everything
260 All of the following print "ok" or "not ok" depending on if the test
271 simple example) and uses that to determine if the test succeeded or
283 $test_name is a very short description of the test that will be printed
284 out. It makes it very easy to find a test in your script when it fails
291 # Failed test 18 (foo.t at line 42)
298 my($test, $name) = @_;
299 $Test->ok($test, $name);
311 determine if the test succeeded or failed. So these:
328 isnt() know what the test was and why it failed. For example this
329 test:
337 # Failed test (foo.t at line 139)
341 So you can figure out what went wrong without rerunning the test.
438 Its advantage over ok() is when the test fails you'll know what $this
442 # Failed test (foo.t at line 12)
480 as one test. If you desire otherwise, use:
533 to safeguard against your test script blowing up.
539 The diagnostics of this test normally just refer to 'the object'. If
607 declare the test ok) or fail (for not ok). They are synonyms for
626 If you pick the right test function, you'll usually get a good idea of
638 test output. Like C<print> @diagnostic_message is simply concatinated
649 # Failed test (foo.t at line 52)
663 interfere with the test.
677 You usually want to test if the module you're testing loads ok, rather
688 These simply use the given $module and test to make sure the load
815 Sometimes running a test under certain conditions will cause the
816 test script to die. A certain function or method isn't implemented
820 but will work in the future (a todo test).
926 Once a todo test starts succeeding, simply move it outside the block.
943 Often a failing test will cause the whole program to die or hang, even
1290 unified backend for any test library to use. This means two test
1321 will throw a warning and exit with 255. If the test died, even after
1328 255 test died
1351 test the internals of string overloaded objects. In this case I would
1388 figure out how to easily wedge test names into Test's interface (along
1407 L<Test::Harness> for details on how your test results are interpreted
1410 L<Test::Differences> for more ways to test complex data structures.
1421 L<Bundle::Test> installs a whole bunch of useful test modules.