Move Test::Simple from lib to ext.
[p5sagit/p5-mst-13.2.git] / ext / Test-Simple / lib / Test / Builder / Module.pm
CommitLineData
b1ddf169 1package Test::Builder::Module;
2
705e6672 3use strict;
4
b1ddf169 5use Test::Builder;
6
7require Exporter;
705e6672 8our @ISA = qw(Exporter);
b1ddf169 9
3e887aae 10our $VERSION = '0.92';
11$VERSION = eval $VERSION; ## no critic (BuiltinFunctions::ProhibitStringyEval)
b1ddf169 12
13# 5.004's Exporter doesn't have export_to_level.
14my $_export_to_level = sub {
ccbd73a4 15 my $pkg = shift;
16 my $level = shift;
17 (undef) = shift; # redundant arg
18 my $callpkg = caller($level);
19 $pkg->export( $callpkg, @_ );
b1ddf169 20};
21
b1ddf169 22=head1 NAME
23
24Test::Builder::Module - Base class for test modules
25
26=head1 SYNOPSIS
27
28 # Emulates Test::Simple
29 package Your::Module;
30
31 my $CLASS = __PACKAGE__;
32
33 use base 'Test::Builder::Module';
34 @EXPORT = qw(ok);
35
36 sub ok ($;$) {
37 my $tb = $CLASS->builder;
38 return $tb->ok(@_);
39 }
40
41 1;
42
43
44=head1 DESCRIPTION
45
46This is a superclass for Test::Builder-based modules. It provides a
47handful of common functionality and a method of getting at the underlying
48Test::Builder object.
49
50
51=head2 Importing
52
53Test::Builder::Module is a subclass of Exporter which means your
54module is also a subclass of Exporter. @EXPORT, @EXPORT_OK, etc...
55all act normally.
56
57A few methods are provided to do the C<use Your::Module tests => 23> part
58for you.
59
60=head3 import
61
62Test::Builder::Module provides an import() method which acts in the
63same basic way as Test::More's, setting the plan and controling
64exporting of functions and variables. This allows your module to set
65the plan independent of Test::More.
66
67All arguments passed to import() are passed onto
68C<< Your::Module->builder->plan() >> with the exception of
69C<import =>[qw(things to import)]>.
70
71 use Your::Module import => [qw(this that)], tests => 23;
72
73says to import the functions this() and that() as well as set the plan
74to be 23 tests.
75
76import() also sets the exported_to() attribute of your builder to be
77the caller of the import() function.
78
79Additional behaviors can be added to your import() method by overriding
80import_extra().
81
82=cut
83
84sub import {
85 my($class) = shift;
ccbd73a4 86
04955c14 87 # Don't run all this when loading ourself.
88 return 1 if $class eq 'Test::Builder::Module';
b1ddf169 89
90 my $test = $class->builder;
91
92 my $caller = caller;
93
94 $test->exported_to($caller);
95
ccbd73a4 96 $class->import_extra( \@_ );
97 my(@imports) = $class->_strip_imports( \@_ );
b1ddf169 98
99 $test->plan(@_);
100
ccbd73a4 101 $class->$_export_to_level( 1, $class, @imports );
b1ddf169 102}
103
b1ddf169 104sub _strip_imports {
105 my $class = shift;
106 my $list = shift;
107
108 my @imports = ();
109 my @other = ();
ccbd73a4 110 my $idx = 0;
b1ddf169 111 while( $idx <= $#{$list} ) {
112 my $item = $list->[$idx];
113
114 if( defined $item and $item eq 'import' ) {
ccbd73a4 115 push @imports, @{ $list->[ $idx + 1 ] };
b1ddf169 116 $idx++;
117 }
118 else {
119 push @other, $item;
120 }
121
122 $idx++;
123 }
124
125 @$list = @other;
126
127 return @imports;
128}
129
b1ddf169 130=head3 import_extra
131
132 Your::Module->import_extra(\@import_args);
133
134import_extra() is called by import(). It provides an opportunity for you
135to add behaviors to your module based on its import list.
136
137Any extra arguments which shouldn't be passed on to plan() should be
138stripped off by this method.
139
140See Test::More for an example of its use.
141
142B<NOTE> This mechanism is I<VERY ALPHA AND LIKELY TO CHANGE> as it
143feels like a bit of an ugly hack in its current form.
144
145=cut
146
ccbd73a4 147sub import_extra { }
b1ddf169 148
149=head2 Builder
150
151Test::Builder::Module provides some methods of getting at the underlying
152Test::Builder object.
153
154=head3 builder
155
156 my $builder = Your::Class->builder;
157
158This method returns the Test::Builder object associated with Your::Class.
159It is not a constructor so you can call it as often as you like.
160
161This is the preferred way to get the Test::Builder object. You should
162I<not> get it via C<< Test::Builder->new >> as was previously
163recommended.
164
165The object returned by builder() may change at runtime so you should
166call builder() inside each function rather than store it in a global.
167
168 sub ok {
169 my $builder = Your::Class->builder;
170
171 return $builder->ok(@_);
172 }
173
174
175=cut
176
177sub builder {
178 return Test::Builder->new;
179}
180
b1ddf169 1811;