Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

test::builder::module(3pm) [osx man page]

Test::Builder::Module(3pm)				 Perl Programmers Reference Guide				Test::Builder::Module(3pm)

NAME
Test::Builder::Module - Base class for test modules SYNOPSIS
# Emulates Test::Simple package Your::Module; my $CLASS = __PACKAGE__; use base 'Test::Builder::Module'; @EXPORT = qw(ok); sub ok ($;$) { my $tb = $CLASS->builder; return $tb->ok(@_); } 1; DESCRIPTION
This is a superclass for Test::Builder-based modules. It provides a handful of common functionality and a method of getting at the underlying Test::Builder object. Importing Test::Builder::Module is a subclass of Exporter which means your module is also a subclass of Exporter. @EXPORT, @EXPORT_OK, etc... all act normally. A few methods are provided to do the "use Your::Module tests =" 23> part for you. import Test::Builder::Module provides an import() method which acts in the same basic way as Test::More's, setting the plan and controlling exporting of functions and variables. This allows your module to set the plan independent of Test::More. All arguments passed to import() are passed onto "Your::Module->builder->plan()" with the exception of "import =>[qw(things to import)]". use Your::Module import => [qw(this that)], tests => 23; says to import the functions this() and that() as well as set the plan to be 23 tests. import() also sets the exported_to() attribute of your builder to be the caller of the import() function. Additional behaviors can be added to your import() method by overriding import_extra(). import_extra Your::Module->import_extra(@import_args); import_extra() is called by import(). It provides an opportunity for you to add behaviors to your module based on its import list. Any extra arguments which shouldn't be passed on to plan() should be stripped off by this method. See Test::More for an example of its use. NOTE This mechanism is VERY ALPHA AND LIKELY TO CHANGE as it feels like a bit of an ugly hack in its current form. Builder Test::Builder::Module provides some methods of getting at the underlying Test::Builder object. builder my $builder = Your::Class->builder; This method returns the Test::Builder object associated with Your::Class. It is not a constructor so you can call it as often as you like. This is the preferred way to get the Test::Builder object. You should not get it via "Test::Builder->new" as was previously recommended. The object returned by builder() may change at runtime so you should call builder() inside each function rather than store it in a global. sub ok { my $builder = Your::Class->builder; return $builder->ok(@_); } perl v5.16.2 2012-10-11 Test::Builder::Module(3pm)

Check Out this Related Man Page

Gtk2::Builder(3)					User Contributed Perl Documentation					  Gtk2::Builder(3)

NAME
Gtk2::Builder HIERARCHY
Glib::Object +----Gtk2::Builder METHODS
builder = Gtk2::Builder->new integer = $builder->add_from_file ($filename) o $filename (localized file name) May croak with a Glib::Error in $@ on failure. integer = $builder->add_from_string ($buffer) o $buffer (string) May croak with a Glib::Error in $@ on failure. integer = $builder->add_objects_from_string ($buffer, $first_object_id, ...) o $buffer (string) o $first_object_id (string) o ... (list) Since: gtk+ 2.14 $builder->connect_signals ($user_data) $builder->connect_signals ($user_data, $package) $builder->connect_signals ($user_data, %handlers) There are four ways to let Gtk2::Builder do the signal connecting work for you: "$builder->connect_signals ($user_data)" When invoked like this, Gtk2::Builder will connect signals to functions in the calling package. The callback names are specified in the UI description. "$builder->connect_signals ($user_data, $package)" When invoked like this, Gtk2::Builder will connect signals to functions in the package $package. "$builder->connect_signals ($user_data, $object)" When invoked like this, Gtk2::Builder will connect signals to method calls against the object $object. "$builder->connect_signals ($user_data, %handlers)" When invoked like this, %handlers is used as a mapping from handler names to code references. $builder->connect_signals_full ($func, $user_data=undef) o $func (scalar) o $user_data (scalar) object = $builder->get_object ($name) o $name (string) list = $builder->get_objects string or undef = $builder->get_translation_domain $builder->set_translation_domain ($domain) o $domain (string or undef) PROPERTIES
'translation-domain' (string : readable / writable / private) The translation domain used by gettext SEE ALSO
Gtk2, Glib::Object COPYRIGHT
Copyright (C) 2003-2008 by the gtk2-perl team. This software is licensed under the LGPL. See Gtk2 for a full notice. perl v5.12.1 2010-07-05 Gtk2::Builder(3)
Man Page