Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

test::unit::procedural(3pm) [debian man page]

Test::Unit::Procedural(3pm)				User Contributed Perl Documentation			       Test::Unit::Procedural(3pm)

NAME
Test::Unit::Procedural - Procedural style unit testing interface SYNOPSIS
use Test::Unit::Procedural; # your code to be tested goes here sub foo { return 23 }; sub bar { return 42 }; # define tests sub test_foo { assert(foo() == 23, "Your message here"); } sub test_bar { assert(bar() == 42, "I will be printed if this fails"); } # set_up and tear_down are used to # prepare and release resources need for testing sub set_up { print "hello world "; } sub tear_down { print "leaving world again "; } # run your test create_suite(); run_suite(); DESCRIPTION
Test::Unit::Procedural is the procedural style interface to a sophisticated unit testing framework for Perl that is derived from the JUnit testing framework for Java by Kent Beck and Erich Gamma. While this framework is originally intended to support unit testing in an object- oriented development paradigm (with support for inheritance of tests etc.), Test::Unit::Procedural is intended to provide a simpler inter- face to the framework that is more suitable for use in a scripting style environment. Therefore, Test::Unit::Procedural does not provide much support for an object-oriented approach to unit testing - if you want that, please have a look at Test::Unit::TestCase. You test a given unit (a script, a module, whatever) by using Test::Unit::Procedural, which exports the following routines into your names- pace: assert() used to assert that a boolean condition is true create_suite() used to create a test suite consisting of all methods with a name prefix of "test" run_suite() runs the test suite (text output) add_suite() used to add test suites to each other For convenience, "create_suite()" will automatically build a test suite for a given package. This will build a test case for each subrou- tine in the package given that has a name starting with "test" and pack them all together into one TestSuite object for easy testing. If you dont give a package name to "create_suite()", the current package is taken as default. Test output is one status line (a "." for every successful test run, or an "F" for any failed test run, to indicate progress), one result line ("OK" or "!!!FAILURES!!!"), and possibly many lines reporting detailed error messages for any failed tests. Please remember, Test::Unit::Procedural is intended to be a simple and convenient interface. If you need more functionality, take the object-oriented approach outlined in Test::Unit::TestCase. AUTHOR
Copyright (c) 2000-2002, 2005 the PerlUnit Development Team (see Test::Unit or the AUTHORS file included in this distribution). All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
o Test::Unit::TestCase o the procedural style examples in the examples directory perl v5.8.8 2006-09-13 Test::Unit::Procedural(3pm)

Check Out this Related Man Page

TestCase(3pm)						  LogReport's Lire Documentation					     TestCase(3pm)

NAME
Lire::Test::TestCase - Common base for Lire test cases. SYNOPSIS
use base qw/Lire::Test::TestCase/; sub set_up { my $self = shift->SUPER::set_up(); $self->{'cfg'}{'lr_schemas_path'} = [ $self->{'tmpdir'} ]; } DESCRIPTION
This package can be used to write test cases for Lire instead of inheriting directly from Test::Unit::TestCase. The default set_up method will create a Lire::Test::HashConfig object and set it up in the configuration framework. This makes it easy to set configuration variables to arbitrary values in the set_up() method. It also sets the LC_MESSAGES locale category to 'C'. If you override set_up() and tear_down() be sure to call the SUPER:: implementation. This subclass also defined a new kind of assertion which make sure that a snippet of code died with a proper error message. assert_died( $test, $regex, [ $msg ] ) Execute $test and fail unless it dies with a message matching $regex. $test should be a reference to CODE. $regex should be a Regexp ref. assert_dies( $regex, $test, [ $msg ] ) Like assert_died() but with a signature closer to the one defined in Test::Unit::Assert. assert_isa( $class, $instance, [ $msg ] ) Fails unless $instance is an instance of $class. FIXTURE RELATED METHOD
lire_default_config_spec() Returns a Lire::Config::ConfigSpec object initialized from the default Lire configuration specification. set_up_tz( $tz ) When you tests uses timelocal() or localtime(), you should use that method to specify the TZ under which it should run. The TZ will be reset to its previous value during tear_down(). set_up_plugin_mgr() This will make the global PluginManager an instance that will only live for the current test. The old PluginManager will be reinstated during tear_down(). This way, you do not need to track calls to register_plugin(). SEE ALSO
Test::Unit::TestCase(3pm) VERSION
$Id: TestCase.pm,v 1.17 2006/07/23 13:16:32 vanbaal Exp $ AUTHORS
Francis J. Lacoste <flacoste@logreport.org> COPYRIGHT
Copyright (C) 2003, 2004 Stichting LogReport Foundation LogReport@LogReport.org This file is part of Lire. Lire is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (see COPYING); if not, check with http://www.gnu.org/copyleft/gpl.html. Lire 2.1.1 2006-07-23 TestCase(3pm)
Man Page